Agent skill

Dev Design

by codeaholicguy in codeaholicguy/ai-devkit

AI DevKit · Design phase guidance for reviewing feature design against requirements.

Apache-2.0Auto-check passedDevelopment

Install Dev Design

skills CLI
$ npx skills add codeaholicguy/ai-devkit --skill dev-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codeaholicguy/ai-devkit dev-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dev-design .claude/skills/dev-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dev-design
GitHub stars
1.6k
Token cost
~793 tokens
SKILL.md length
398 words
Files
2
Skills in repo
28
Repo updated
First seen
Licence
Apache-2.0

At a glance

AI DevKit · Design phase guidance for reviewing feature design against requirements.

  • Works in 8 steps: Run npx ai-devkit@latest lint before… → If working on a named feature, run npx… → Read existing requirements and design… → …
  • The user wants to validate architecture
  • SKILL.md covers Phase Contract and Review Design
  • Calls npx

What it does

Dev Design is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Design phase guidance for reviewing feature design against requirements. Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Architecture decision records and Software architecture. The repository describes itself as: The control plane for AI coding agents. The licence is Apache-2.0.

When your agent uses it

  • The user wants to validate architecture
  • Review design docs
  • Resolve design trade-offs
  • Run dev-lifecycle phase 3

Example prompts

  • “/dev-design”

Requirements

  • Node.js

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Run npx ai-devkit@latest lint before phase work.
  2. If working on a named feature, run npx ai-devkit@latest lint --feature .
  3. Read existing requirements and design docs before changes.
  4. Ask until every material architecture, scope, validation, rollout, contradiction, trade-off, or open question is answered, explicitly…
  5. Ask one decision at a time, with why it matters, 2-3 viable options when useful, and a recommended answer.
  6. Do not approve or transition past design while material open questions remain.
  7. Use mermaid diagrams for architecture visuals where a diagram clarifies the design.
  8. If parent dev-lifecycle established usable task tracing, emit design phase, progress, blocker/open-question, and next-step events per task.

What it can do on your machine

Read from SKILL.md and the folder at commit 7ef0cd5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dev Design loads about 793 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 398 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~793

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from codeaholicguy/ai-devkit at commit 7ef0cd5, republished under its Apache-2.0 licence (© codeaholicguy). 398 words, ~793 tokens.

Download SKILL.mdSave it as .claude/skills/dev-design/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
dev-design
description
AI DevKit · Design phase guidance for reviewing feature design against requirements. Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3.

Dev Design

Run the design review phase for configured AI docs features. Before changing docs or code, propose the concrete plan for this phase and wait for user approval unless the user already approved the exact phase plan.

Phase Contract

  1. Run npx ai-devkit@latest lint before phase work.
  2. If working on a named feature, run npx ai-devkit@latest lint --feature <name>.
  3. Read existing requirements and design docs before changes.
  4. Ask until every material architecture, scope, validation, rollout, contradiction, trade-off, or open question is answered, explicitly deferred, or accepted as a named assumption.
  5. Ask one decision at a time, with why it matters, 2-3 viable options when useful, and a recommended answer.
  6. Do not approve or transition past design while material open questions remain.
  7. Use mermaid diagrams for architecture visuals where a diagram clarifies the design.
  8. If parent dev-lifecycle established usable task tracing, emit design phase, progress, blocker/open-question, and next-step events per task.

Review Design

Use for Phase 3.

  1. Run npx ai-devkit@latest lint --feature <name> and review the design doc path it validates. If manual path resolution is unavoidable, first resolve .ai-devkit.json paths.docs, falling back to docs/ai.
  2. Search memory for relevant architecture patterns or past decisions.
  3. Cross-check against the latest matching requirements doc. Verify every goal, user story, and constraint has corresponding design coverage. Flag uncovered requirements.
  4. Review completeness: architecture, components, technology choices, data models, API contracts, design trade-offs, and non-functional requirements.
  5. Check usage-first design: APIs, CLI flows, UI flows, and docs should optimize for their caller/user, not implementation convenience.
  6. Screen design red flags: shallow modules, pass-through layers, temporal decomposition, leaked transport/storage/framework types, scattered validation, synchronized flags, and repeated conditionals where a domain model would fit.
  7. Resolve every gap, misalignment, open question, hidden assumption, or unresolved trade-off between requirements and design.
  8. Brainstorm alternatives for key architecture decisions and trade-offs before accepting the first approach.
  9. Prefer subtract-before-add sequencing: delete obsolete paths, consolidate redundant concepts, and narrow scope before adding new structure.
  10. Update the design doc with clarified decisions and chosen options.
  11. Store reusable architecture decisions in memory.
  12. If task tracing is available, record design coverage progress, next step, or blockers per task.
  13. Summarize requirements coverage, completeness assessment, updates made, and remaining gaps.
Show full SKILL.md (19 more words)Show less

Next: dev-implementation. If requirements gaps are found, return to dev-requirements. If design is fundamentally wrong, revise design and re-review.

© codeaholicguy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/dev-design of codeaholicguy/ai-devkit.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 7ef0cd5

Compare with similar skills

Dev Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dev Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dev Design this skillcodeaholicguy/ai-devkit1.6k—~793Automated safety check: PassApache-2.0
Create Vibe Featuremistralai/mistral-vibe5.1k—~1.2kAutomated safety check: PassApache-2.0
Architecture Decisions and ADRsfirst-fluke/oh-my-agent1.3k—~2.6kAutomated safety check: PassMIT
Light System DesignLight0305/Light-skills640—~3.6kAutomated safety check: PassMIT
Architecture DesignerAratKruglik/claude-laravel1551 repos~895Automated safety check: PassNone
Architecture Decision Record Writerdralgorhythm/claude-agentic-framework124—~529Automated safety check: PassNone

Similar skills

  • Create Vibe Feature

    mistralai/mistral-vibe

    Official

    Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.

    5.1k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Architecture Decisions and ADRs

    first-fluke/oh-my-agent

    Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.

    1.3k GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Light System Design

    Light0305/Light-skills

    Evidence-based workflow for designing or modernizing a software system: current-state inventory, options, API and schema contracts, migration plans, ADRs and verification.

    640 GitHub stars~3.6k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • Architecture Designer

    AratKruglik/claude-laravel

    A skill your agent uses when designing new system architecture, reviewing existing designs, or making architectural decisions.

    155 GitHub starsUsed in 1 repo~895 tokens
    DevelopmentAuto-check passed
  • Architecture Decision Record Writer

    dralgorhythm/claude-agentic-framework

    Writes Architecture Decision Records with title, status, context, decision, rationale and consequences for significant technical choices, kept short and numbered.

    124 GitHub stars~529 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Architecture Review

    extra-org/extra

    Guard the project's architecture invariants. An agent skill from extra-org/extra.

    113 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from codeaholicguy/ai-devkit

All 28 skills in this repo
  • Agent Management

    codeaholicguy/ai-devkit

    AI DevKit · Manage running AI agents with ai-devkit agent commands.

    1.6k GitHub stars~558 tokensUpdated yesterday
    Auto-check passed
  • Dev Lifecycle

    codeaholicguy/ai-devkit

    AI DevKit · Orchestrator for structured SDLC phase skills. An agent skill from codeaholicguy/ai-devkit.

    1.6k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Task

    codeaholicguy/ai-devkit

    AI DevKit · Track dev-lifecycle / structured-debug progress on a durable task with the ai-devkit task CLI.

    1.6k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Simplify Implementation

    codeaholicguy/ai-devkit

    AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability.

    1.6k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Agent Communication

    codeaholicguy/ai-devkit

    AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send.

    1.6k GitHub stars~321 tokensUpdated yesterday
    Auto-check passed
  • Technical Writer

    codeaholicguy/ai-devkit

    AI DevKit · Review and improve documentation for novice users.

    1.6k GitHub stars~431 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Dev Design

What does Dev Design do?

AI DevKit · Design phase guidance for reviewing feature design against requirements. Dev Design is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Design phase guidance for reviewing feature design against requirements.

When should I use Dev Design?

Dev Design fits situations like: the user wants to validate architecture; review design docs; resolve design trade-offs; run dev-lifecycle phase 3.

How do I install Dev Design in Claude Code?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-design -a claude-code`. Or copy the skill folder (skills/dev-design in codeaholicguy/ai-devkit) into .claude/skills/dev-design in your project. Claude Code loads it when a task matches its description.

How do I install Dev Design in Codex?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-design -a codex`. Or copy the skill folder (skills/dev-design in codeaholicguy/ai-devkit) into .agents/skills/dev-design in your project. Codex loads it when a task matches its description.

Can I use Dev Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codeaholicguy/ai-devkit --skill dev-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-design, .gemini/skills/dev-design, .github/skills/dev-design and .opencode/skills/dev-design in your project.

What does Dev Design need to run?

Going by SKILL.md and its folder, Dev Design needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Dev Design access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dev Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dev Design use?

Dev Design is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dev Design use?

About 793 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dev Design?

Skills that share tags, products or a category with Dev Design: Create Vibe Feature (mistralai/mistral-vibe, 5.1k stars), Architecture Decisions and ADRs (first-fluke/oh-my-agent, 1.3k stars), Light System Design (Light0305/Light-skills, 640 stars) and Architecture Designer (AratKruglik/claude-laravel, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Design?

codeaholicguy (a GitHub user) maintains it in codeaholicguy/ai-devkit, which has 1,641 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 6, 2026.

Source: codeaholicguy/ai-devkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.