development-workflow

Included with Lifetime

$97 forever

This skill bridges the gap between scaffolding and active development. It should be used when the user says "start development", "begin building", "ready to code", "what's next after scaffolding", "what do I do now", "development checklist", "start coding", "how do I start", "check readiness", "run development checks", or "readiness report". It also applies when the user has just finished scaffolding with init-prototype and wants to begin building features.

Design

What this skill does

# Development Workflow Bridge

Run automated checks on the current prototype monorepo and present an actionable
development checklist. This skill connects the scaffolding phase to active development
by verifying readiness and prescribing the correct skill chain.

## Step 0: Verify Monorepo

First verify `packages/` exists. If not, inform the user this skill requires a monorepo
scaffolded by `prototyping-skills:init-prototype` and suggest running that skill first.

## Step 1: Assess Current State

Run these checks automatically:

### Detect packages

```bash
ls packages/
```

### Check test infrastructure per package

For each detected package, check if `tests/` directory exists:

```bash
for pkg in packages/*/; do
name=$(basename "$pkg")
if [ -d "$pkg/tests" ]; then
count=$(find "$pkg/tests" -name "*.test.ts" | wc -l)
echo "$name: $count test files"
else
echo "$name: NO TEST INFRASTRUCTURE"
fi
done
```

### Run existing tests

```bash
bun test 2>&1 || echo "Tests failed or no tests found"
```

### Check lint status

```bash
bunx @biomejs/biome check . 2>&1 | tail -5
```

### Check CI configuration

```bash
if [ -f .github/workflows/ci.yml ]; then
echo "CI: configured"
grep -q "bun test" .github/workflows/ci.yml && echo "CI includes tests" || echo "CI MISSING test step"
else
echo "CI: NOT CONFIGURED"
fi
```

## Step 2: Report Findings

Present results as a readiness report:

```
## Development Readiness Report

### Packages Detected
List each package found by `ls packages/` with its status. Only include packages that exist.

### Test Infrastructure
- [package]: [X test files | NO TESTS]

### Lint Status
- [pass/fail with summary]

### CI
- [configured with tests | configured without tests | not configured]
```

## Step 3: Recommend Actions

Based on findings, recommend specific actions:

### Missing test infrastructure

If any package lacks a `tests/` directory:

> Run `prototyping-skills:generate-tests` to scaffold test infrastructure for packages missing tests.

### No test files

If test directories exist but contain no `.test.ts` files:

> Start with `superpowers:test-driven-development` to write tests alongside new features.

### Lint failures

If Biome reports issues:

> Run `bun run fix` to auto-fix lint and formatting issues before starting development.

### CI missing test step

If `.github/workflows/ci.yml` lacks `bun test`:

> Add `- run: bun test` to the CI workflow to gate merges on passing tests.

## Step 4: Present the Development Workflow

After reporting state, present the prescribed workflow:

```
## Prescribed Development Workflow

### Adding a Feature
1. Write tests first — use `superpowers:test-driven-development`
2. Implement the feature in the appropriate package
3. Run `code-simplifier:simplify` before committing (enforced by pre-commit hook)
4. Run `superpowers:verification-before-completion` to verify completeness
5. Run `superpowers:requesting-code-review` before merging

### After a Burst Session
Before merging, run the full verification chain:
1. `bun check` (Biome lint + format)
2. `bun test` (all packages)
3. `superpowers:verification-before-completion`
4. `superpowers:requesting-code-review`
```

## Step 5: Quick-Reference Skill Map

Present available skills by development phase:

```
## Available Skills by Phase

### Planning
- `superpowers:writing-plans` — Structure implementation plans
- `superpowers:brainstorming` — Explore ideas and approaches

### Building
- `superpowers:test-driven-development` — TDD workflow (write test → implement → refactor)
- `superpowers:dispatching-parallel-agents` — Parallelize independent tasks
- `prototyping-skills:generate-api` — Add API routes
- `prototyping-skills:generate-ui` — Add UI pages/components
- `prototyping-skills:generate-mcp` — Add MCP tools

### Finishing
- `code-simplifier:simplify` — Review code for quality and efficiency
- `superpowers:verification-before-completion` — Verify work is complete
- `superpowers:requesting-code-review` — Get code review before merge
- `superpowers:finishing-a-development-branch` — PR/merge/cleanup workflow
```

## Behavior

This skill is **active, not passive**. When triggered:

1. Immediately run the assessment checks (Step 1)
2. Present the readiness report (Step 2)
3. Recommend specific actions based on findings (Step 3)
4. Always show the prescribed workflow and skill map (Steps 4-5)
5. Ask the user what they want to build first

Files: 1

Size: 4.9 KB

Complexity: 17/100

Category: Design

Source: https://github.com/kjgarza/marketplace-claude/tree/main/plugins/prototyping-skills/skills/development-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