develop
Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.
Install / Use
npx skills add jsmastery-pro/skills --skill developInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of develop
develop scores 85/100 on our quality scale, 431st of 642 Marketing skills we index.
Its SKILL.md is 15 KB long, well organised into 17 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 1,318 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
develop compared with similar skills
All 4 of these similar skills score higher than develop; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| develop (this skill)by jsmastery-pro | 85 | 1.3k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install develop?
- Run
npx skills add jsmastery-pro/skills --skill develop. The install tabs above show the steps for each supported agent. - Which AI agents does develop work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is develop safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is develop still maintained?
- The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: develop allowed-tools: Bash, Read, Grep, Glob, Write, Edit, Agent, AskUserQuestion description: "Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope."
Output style (plain words, no dashes, no hyphens)
<!-- OUTPUT-STYLE:START -->Write everything this skill produces, files and messages alike, in plain simple language. Talk to the reader as you, warm and direct like a colleague, and present every step as a recommendation they may run or skip, never an order. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only, not read-only. Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. Use short sentences, commas, or parentheses. Clear beats clever.
What this skill does
The builder: turns a spec plus project conventions into working code. Tracks: UI (components, pages, layouts; ui-guide.md), Logical (APIs, services, data layers, business logic, integrations; logical-guide.md), or both (e.g. "auth" = sign in pages plus session logic → run both). Step 0 gates on the spec so load bearing choices (an auth approach, a payment provider) are decided in /architect, not silently invented partway through the build.
Asks vs acts
Gates, then acts: no upfront question rounds like /architect. Read the decision, build, ask only what the design left open (the visual direction when no reference was given; a business rule the spec didn't settle). Infer from the spec, AGENTS.md, and codebase; recommend local implementation choices.
Artifact ownership
- Writes app code (plus CSS/tokens for UI).
- Scope (
docs/scope/): only the Step 4 touches (feature status →in-progress, milestone sub boxes,Build itbox, code pointer). Marks a featuredoneonly at thePrototypeworkflow tier (build plus its own self check; the engineer opted out of separate verification); anAssumedspec does not block this, it stays flagged as owing ratification. AtAlpha/Beta/GAit leaves the featurein-progressfor/check verifyand/testto close, and never ticksVerify itorTest it. Never creates files indocs/scope/(scopes only; analysis/research is/architect's, in the spec'srationale.md). - Never writes spec content or deliberates a decision (flags the need, defers to
/architect); never restructures rootAGENTS.md(that's/audit); new area conventions go via/syncafterwards. One narrow exception: onBuild now, record it as an assumed spec(Step 0),/developmay create a spec, but only inStatus: Assumed, and only the assumption record fields (owed decision, assumption built on, authorized by, code area, requirements seeds). It never writes rationale and never advances anAssumedspec past that state;/architectowns clearing it. This is the only spec/developcreates. - One spec touch on an existing spec: the
**Status**:line (umbrella decision → theindex.md's, never a child's), plus filling the feature's spec pointer line. Build start:Proposed→In Progress; build lands (feature →done):In Progress→Accepted(a spec is notAccepteduntil its feature ships). Never edit spec content, only that line, surgically: read it again right before writing; unexpected state (alreadyAccepted,Superseded) → flag, don't clobber. Never move a spec out ofAssumed(that is ratification,/architect's job): anAssumedspec staysAssumedthrough the build even while the feature isin-progress, so it can never reachAccepteduntil/architectratifies it. The feature itself can still be markeddone(the engineer's call); theAssumedspec stays flagged as owing ratification, it does not blockdone. - Artifact base:
docs/by default,.workflow/ifdocs/is a published docs site. Read from whichever exists (paths here assumedocs/). - Shared scope: read it again right before ticking, edit only the specific checkbox, status, or pointer line (never rewrite the file); feature not as expected (already
done, reworked) → flag, don't overwrite.
Portability (any OS, any agent)
Any Agent Skills client, macOS/Linux/Windows. Detection snippets are POSIX reference; use your agent's own cross platform file tools. Builds inline on the main thread (Step 3); the only subagents are a read only scout that explores code (Step 2.5) and a read only researcher for a doc check (Step 2.6, degrading to building from knowledge without web capability), both on the cheapest model. Bundled guides (ui-guide.md, logical-guide.md, checklist.md) and the build flow after the gate (flow/build.md) are paths relative to this skill's folder; the main thread reads them. No interactive question picker → ask the prompts as plain text with the same options.
Execution
Before you build: the project must already exist (except the scaffold task)
Exception: if this IS the scaffold sub task of the Stack and architecture foundation feature (prompt says scaffold, or the step initializes the project from the stack spec), creating the project IS the job. Read the ARCHITECTURE spec's ## Proposed stack; run the framework's own project initializer for the stack the spec names; install base dependencies (framework, core runtime, only what the first slice needs); lay out directories; confirm a dev server or build runs. Keep the repo the initializer creates (never discard it when relocating the project); if it made none and git integration is on, git init. Scaffold steps derive from the stack decision (a decision spec has no build plan). Install just in time: NOT every library the spec names (email, monitoring, and so on); each later feature installs its own when built; only cross cutting tooling (lint, format, type strictness) comes early, via /audit + the tooling task. Then proceed.
Otherwise /develop builds into an existing project. No skeleton (no package.json/pyproject.toml/go.mod/manifest, no source tree) and not the scaffold task → stop:
No project found to build into. Run the scaffold step first (the Stack and architecture feature's scaffold sub task, per your architecture spec), then run
/developagain.
A project exists (even a bare scaffold) → proceed.
Before you build: freshness & collaboration (don't build on stale state or over a teammate)
Before mutating anything (skip silently if solo, offline, or not using git): git fetch quietly; base = main, else master; behind count (git rev-list --count HEAD..origin/<base>); uncommitted work (git status --short).
- Behind (count > 0) → stop and warn: "You're N commits behind
origin/$BASE. A teammate may have already changed or shipped this. Pull first, then run again." - Uncommitted work in the area you'll touch → warn: "You have uncommitted changes here. Commit or stash first so this build doesn't tangle with them." Let them proceed if they insist.
- Feature
in-progressin the scope AND its code area (pointer line's path) has recent commits by another author (git log --format='%an' -- <area>) → warn: "<feature> looks like it's partway through the build by someone else. Coordinate before continuing it." Confirm before proceeding.
Warnings, not hard blocks, but surface them.
Git integration: if the nearest AGENTS.md ## Git says integration: on, read flow/git.md and follow it (branch before building, commit as milestones land); absent or off → do no active git.
Step 0: The spec gate (always first)
Is a decision owed and unrecorded? Do NOT judge this by introspection ("do I feel like I'm inventing something?"), the build model rationalizes a real decision as "just wiring" and waves it through. Use a positive input coverage test, which is mechanical and harder to talk yourself out of:
Enumerate every value this build must produce, compute, or display (from the acceptance criteria and the spec's design). For each, does the spec name where it comes from (an input, a DB column, a derivation from a named value, a prior decision)? Any required value with no named source is an owed decision.
If any source is unnamed, stop and route to the gate (/architect, or record an Assumed spec; /develop implements decisions, it doesn't make them). A decision is also owed when you'd have to invent:
- A provider, library, integration, data model, or cross cutting pattern (e.g. auth provider, DB/ORM, caching strategy).
- A whole UI page or screen: its design system (
design.mdthere? if not, which direction?), sections/composition, component inventory, asset strategy (no screenshot, no repo images → e.g. an online source). Owed unless adesign.mdAND a page level spec pin these down. - A feature's behavior (search, a wizard: "what exactly should it do?" is open;
/architectasks those questions). Owed unless a spec defines it.
What "local implementation detail" actually means (the narrow exception): ONLY a choice among options the spec's named sources already permit, a loop style, a variable name, which helper to call. The moment a choice determines a value's source, or a behavior an acceptance criterion constrains, it is load bearing by definition, however small it looks. Deriving "the user's today from the timezone on their last read row" is not a local detail: it picks the source of a value an AC constrains, so it is owed. NOT owed for genuine pure implementation: a small bug fix, a component matching an existing design.md, wiring pieces whose sources the spec already names, a copy tweak, anything an existing spec/design.md/AGENTS.md fully governs.
Don't hardcode to page names or to any one example (timezone is an illustration of the pattern, not a rule); apply the input coverage test to whatever was asked. False negatives are the failure mode, building a real decision without noticing: when a required value's source is unnamed, or you are unsure, treat as owed and ask (panel below).
Read only what this feature needs, never the whole docs/ tree: its one scope file and its one governing spec (single file, or umbrella index.md plus the one child speccing this sub task). No other features' rows, scope files, workspaces, or unrelated specs.
Check, in order:
- Locate this feature's scope file (only that one). Monorepo →
docs/scope/<workspace>/for the task's package. Pick the file (scope.md, or the matching<epic>.mdin a split) from the At a glance table alone; read just this feature's section.needs a decisionwith no spec pointer yet → decision owed and missing. Malformed → flag and ask, don't guess. - Open the governing spec via the feature's
specpointer, reading only its build spec sections as defined in the build flow (flow/build.md), Step 2 item 1. Found → it's the spec; proceed. No pointer and no linked spec → targeted look indocs/specs/<workspace>/for one matching this feature's scope, never a blanket read. - The nearest
AGENTS.md(workspace/area) may already capture the decision, synced from an earlier feature (e.g. "the auth provider is already chosen") → proceed without a new spec.
Decision owed and unrecorded → don't guess, don't silently stop. Ask (single select; AskUserQuestion on Claude Code):
- question: "This looks like it needs an architecture decision first:
<name the specific load-bearing choice, e.g. 'which auth provider + session model'>. How do you want to handle it?" - header: "spec first?"
- options:
Architect it first: "Recommended. Capture the decision in a spec before buil
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
