makefile-workflow

Included with Lifetime

$97 forever

Design or update Makefiles with consistent build, format, lint, test, and check-* targets. Use when a user asks for a Makefile, build automation, or project workflow targets for Go, Node, Bazel, or mixed stacks.

Design

What this skill does


# Makefile Workflow

Create or refine Makefiles that encode a reliable developer workflow. Mirror the project's existing tooling (Go, Node, Bazel, Supabase, etc.) and use low-noise output for successful runs.

## Instructions

1. Ask for essentials if missing:
   - Primary language(s) and tooling (Go, Node, Bazel, Python, etc.)
   - Lint/format/test commands already in use
   - Whether the project wants `all`, `check`, and `fix` targets
2. Start with a clear, consistent target taxonomy:
   - `all`: full local workflow (format + fix + tests + build + check-* targets)
   - `check`: CI-friendly checks (no mutation), prefer `check-*` targets
   - `format` + `check-format`
   - `lint` + `fix`
   - `test`, `build`, `coverage`, `clean`
3. Use the stricter naming convention for non-mutating checks:
   - Prefer `check-*` over names like `type-check`, `bundle-check`
   - Example: `check-astro`, `check-bundle`
4. Reduce output noise for successful runs:
   - If the repo has `scripts/quiet-run.sh`, wrap commands like:
     `@./scripts/quiet-run.sh "Label" <command>`
   - Only use it where the project already does; don't invent a helper without asking.
5. Use `.PHONY` for non-file targets and group related sections with comments.
6. Keep shell-safe loops and cross-platform sed where needed:
   - Prefer `rg` for file lists.
   - Avoid scanning `node_modules` or vendor directories.
7. For Go projects, include `golangci-lint` verification hashes if `.golangci.yml` is present.
8. For frontend projects, prefer `npm run <task>` or `pnpm run <task>` to preserve project scripts.
9. If generation or formatting changes files, add `check-generated` or `check-format` that fails on a dirty git diff.
10. For large repos, consider stamp files to avoid repeated work.
11. Ensure Makefiles work correctly with `make -j` (parallel execution):
    - Targets that modify files (e.g., `format`, `fix`) must declare dependencies to prevent concurrent writes. For example, `fix` should depend on `format` since both write to the same files.
    - Validation or check targets that run after writes should depend on the write targets. For example, `validate-full` should depend on `fix`.
    - Read-only targets (e.g., `check-format`, `lint`, `test`) are safe to run in parallel and need no extra ordering.
    - If correct ordering cannot be expressed through dependencies, add `.NOTPARALLEL` to the Makefile.

## Recommended target patterns

### Minimal workflow
- `all`: `format fix test build`
- `check`: `check-format lint test build`
- Parallel-safety deps: `fix: format` (both mutate files)

### Go + linters
- `lint-golangci`, `fix-golangci`, `verify-golangci-config`
- `coverage`, `coverage-html`, `coverage-report`, `clean-coverage`

### Frontend + Supabase
- `check-astro`, `check-bundle`, `test-e2e`, `db-push`, `db-reset`, `db-status`, `db-gen-types`

## Output expectations

When asked to create or update a Makefile:
- Produce a ready-to-run Makefile tailored to the project.
- Preserve existing targets and semantics; only add or adjust as needed.
- Call out any assumptions (package manager, tools, coverage thresholds).

Files: 1

Size: 3.3 KB

Complexity: 12/100

Category: Design

Source: https://github.com/jaeyeom/claude-toolbox/tree/main/plugins/makefile-workflow/skills/makefile-workflow

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts