Implement
Implement an app from its design docs, either a SPEC.md or the ONTOLOGY.md + CRITERIA.md set (with DYNAMICS and RATIONALE), in order (contract, then headless core and tests, then tuning, then UI), then review JS and CSS and reconcile the docs. Use after creating or updating a SPEC.md or ONTOLOGY.md.
Install
npx skills add roby2358/skills --skill implementgit clone --depth 1 https://github.com/roby2358/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/implement ~/.claude/skills/implementPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Implement Workflow Build an app from its design documents in a fixed order: contract and tests first, then the headless core, then measured tuning, then UI, then reviews and doc reconciliation. Use subagents for the review tasks. ## Required Input An app path (e.g. `balance`, `survive`, or a full path). ## Step 0: Find the spec format Look in the app directory: | Found | Format | Implementation reference | Checks come from | "Why" lives in | |---|---|---|---|---| | `ONTOLOGY.md` | **Design-doc set** | ONTOLOGY (§0 purpose / goals / priorities / non-goals, then entities, state, rules as pseudocode, commands and events, numbers) | CRITERIA (R-* rule tables, U-* UI checks, X-* playtest criteria) | RATIONALE (D-* decisions, Q-* open questions); DYNAMICS for intent; ONTOLOGY §0 (or a legacy TELOS.md) breaks ties | | `SPEC.md` only | **SPEC** | SPEC.md | SPEC's acceptance / examples sections, or derived from its rules | SPEC's notes, if any | | Neither | Stop | Ask the user to write a spec first (`specification` or `game-design` skill) | | | If both exist, ONTOLOGY wins; treat SPEC.md as legacy and say so. ## Step 1: Pre-flight (do not write code yet) - **Open questions.** Read RATIONALE's Q-* list (or SPEC's open questions). If any are unanswered and block a rule, batch them to the user in one message and stop. - **Provenance.** Treat items tagged **[P]** (proposed by Claude) as provisional and
Details
- Skill name
implement- Repository
- roby2358/skills
- Path
implement/SKILL.md- Repo updated
- 14 November 2026
FAQ
What does the Implement skill do?
Implement an app from its design docs, either a SPEC.md or the ONTOLOGY.md + CRITERIA.md set (with DYNAMICS and RATIONALE), in order (contract, then headless core and tests, then tuning, then UI), then review JS and CSS and reconcile the docs. Use after creating or updating a SPEC.md or ONTOLOGY.md.
How do I install the Implement skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add roby2358/skills --skill implement. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Implement popular?
It lives in roby2358/skills, which has 5 GitHub stars and 0 forks.
Related skills
Coding
5roby2358/skills
Project-specific coding conventions and constraints. Use when writing, modifying, or refactoring any code, implementing features, writing tests, or building MCP servers in this project.
Game Design
5roby2358/skills
Design principles for tactics and strategy games. Use when designing new mechanics, tuning existing systems, adding units or abilities, adjusting difficulty, or making any game design decision. Triggers on discussions about game balance, unit roles, terrain, pacing, spawning, healing, combat, win/loss conditions, or UI for conveying game state.
Game Productize
5roby2358/skills
Audit a browser game for ship-readiness and produce a tiered gap list: a SHIP.md in the game repo plus pjpd tasks. Finds what gets forgotten between "the game works" and "a stranger can play it": title/menus/end screens, save and resume, audio and settings, onboarding, the mobile "sorry" screen, localization readiness, error recovery, hosting on the author's site and on portals (itch.io, Newgrounds), credits, asset licenses, and AI disclosure. Use when the user says "productize", "/game-productize", "get this game ready to ship/release/publish/launch", "what's missing before I launch", "prep f
Integration Health Check
9sandbaseai/workbuddy-skill
Use first when an integration context is ambiguous or a user needs to verify connection, credentials, accessible organizations, projects, or capabilities before taking an action.
Landing Page Conversion Audit
9sandbaseai/workbuddy-skill
Audit a landing page, sales page or checkout page for conversion leaks and return a fix list ordered by expected revenue impact. Use when asked to review, critique or improve a landing page, sales page, opt-in page, product page or checkout flow, when conversion rate is low, when paid traffic is not converting, or when someone asks "why isn't this page converting" or wants a CRO / landing page review.
Frontend Review
9sandbaseai/workbuddy-skill
Use when reviewing frontend changes for interaction correctness, responsive behavior, accessibility, performance, state handling, and browser-facing regressions.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.