Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
Activate the Super Dev pipeline inside Codex CLI. An agent skill from shangyankeji/super-dev.
Install Super Dev
$ npx skills add shangyankeji/super-dev --skill super-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shangyankeji/super-dev super-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shangyankeji/super-dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/super-dev .claude/skills/super-dev && rm -rf skills-srcUse ~/.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/
Install the "super-dev" agent skill from https://github.com/shangyankeji/super-dev/tree/main/.agents/skills/super-dev into .claude/skills/super-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "super-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shangyankeji/super-dev/tree/main/.agents/skills/super-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shangyankeji/super-dev --skill super-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shangyankeji/super-dev super-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shangyankeji/super-dev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/super-dev .agents/skills/super-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "super-dev" agent skill from https://github.com/shangyankeji/super-dev/tree/main/.agents/skills/super-dev into .agents/skills/super-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "super-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shangyankeji/super-dev --skill super-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shangyankeji/super-dev super-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shangyankeji/super-dev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/super-dev .cursor/skills/super-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "super-dev" agent skill from https://github.com/shangyankeji/super-dev/tree/main/.agents/skills/super-dev into .cursor/skills/super-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "super-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shangyankeji/super-dev.git --path .agents/skills/super-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shangyankeji/super-dev --skill super-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shangyankeji/super-dev super-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shangyankeji/super-dev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/super-dev .gemini/skills/super-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "super-dev" agent skill from https://github.com/shangyankeji/super-dev/tree/main/.agents/skills/super-dev into .gemini/skills/super-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "super-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shangyankeji/super-dev super-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shangyankeji/super-dev --skill super-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shangyankeji/super-dev.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/super-dev .github/skills/super-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "super-dev" agent skill from https://github.com/shangyankeji/super-dev/tree/main/.agents/skills/super-dev into .github/skills/super-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "super-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shangyankeji/super-dev --skill super-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shangyankeji/super-dev super-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shangyankeji/super-dev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/super-dev .opencode/skills/super-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "super-dev" agent skill from https://github.com/shangyankeji/super-dev/tree/main/.agents/skills/super-dev into .opencode/skills/super-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "super-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
super-dev- GitHub stars
- 273
- Token cost
- ~2.1k tokens
- SKILL.md length
- 798 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Activate the Super Dev pipeline inside Codex CLI. An agent skill from shangyankeji/super-dev.
- Works in 4 steps: 图标系统: 功能图标只能来自 Lucide / Heroicons /… → AI 模板化禁令: 禁止紫/粉渐变主色调、禁止 emoji… → 代码即交付: 不允许“先用 emoji 顶上后面再换”。图标库必须在第一行 UI… → …
- Testing & QA work in your project
- SKILL.md covers 关键约束提醒（每次操作前必读）, Direct Activation Rule（强制）, 触发方式（强制） and Runtime Contract（强制）, plus 13 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Super Dev is an agent skill from shangyankeji/super-dev. Activate the Super Dev pipeline inside Codex CLI.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA. The repository describes itself as: Engineering workflow layer for AI coding tools with specs, review, quality gates, and traceability.为 AI 编程工具提供工程化流程、质量门禁与可追溯能力。 The licence is MIT.
When your agent uses it
- Testing & QA work in your project
Example prompts
- “/super-dev”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 图标系统: 功能图标只能来自 Lucide / Heroicons / Tabler 图标库。绝对禁止使用 emoji 表情 作为功能图标、装饰图标或临时占位。如果你发现自己即将输出包含 emoji 的 UI 代码，停下来，改用图标库组件。
- AI 模板化禁令: 禁止紫/粉渐变主色调、禁止 emoji 图标、禁止无信息层级的卡片墙、禁止默认系统字体直出。
- 代码即交付: 不允许“先用 emoji 顶上后面再换”。图标库必须在第一行 UI 代码前就锁定。
- 自检规则: 在向用户展示任何 UI 代码或预览前，必须自检源码中不存在任何 emoji 字符（Unicode range U+2600-U+27BF, U+1F300-U+1FAFF）。发现后先替换为正式图标库再继续。
What it can do on your machine
Read from SKILL.md and the folder at commit d06e640. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Super Dev loads about 2.1k tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 798 words of instructions outside code blocks.
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 shangyankeji/super-dev at commit d06e640, republished under its MIT licence (© shangyankeji). 798 words, ~2,093 tokens.
Download SKILL.mdSave it as
.claude/skills/super-dev/SKILL.md (or your agent's skills folder).- name
- super-dev
- description
- Activate the Super Dev pipeline inside Codex CLI.
- when_to_use
- Use when the user says /super-dev, super-dev:, or super-dev： followed by a requirement. Activate the Super Dev pipeline for research-first, commercial-grade…
- version
- 2.4.0
super-dev for Codex CLI
关键约束提醒（每次操作前必读）
以下规则在整个开发过程中始终有效，不得以任何理由违反：
图标系统: 功能图标只能来自 Lucide / Heroicons / Tabler 图标库。绝对禁止使用 emoji 表情 作为功能图标、装饰图标或临时占位。如果你发现自己即将输出包含 emoji 的 UI 代码，停下来，改用图标库组件。
AI 模板化禁令: 禁止紫/粉渐变主色调、禁止 emoji 图标、禁止无信息层级的卡片墙、禁止默认系统字体直出。
代码即交付: 不允许“先用 emoji 顶上后面再换”。图标库必须在第一行 UI 代码前就锁定。
自检规则: 在向用户展示任何 UI 代码或预览前，必须自检源码中不存在任何 emoji 字符（Unicode range U+2600-U+27BF, U+1F300-U+1FAFF）。发现后先替换为正式图标库再继续。
Direct Activation Rule（强制）
- If this skill is invoked, Super Dev pipeline mode is already active.
- Do not spend a turn saying you will read the skill first, explain the skill, or decide whether to enter the workflow.
- Do not answer with variants of "我先读取 skill 再判断流程".
- If this file is loaded from
~/.codex/skills, treat it as the compatibility mirror of the same Super Dev contract.
触发方式（强制）
- Treat
super-dev: <需求描述>andsuper-dev：<需求描述>as the AGENTS-driven natural-language fallback entry point. - Treat
$super-devas the explicit official Skill mention when the Codex host exposes skills by name. - In Codex desktop/app, if the slash list shows this enabled skill, selecting
/super-devfrom that list is valid because it resolves to this Skill rather than a custom project slash command. - Do not treat it as ordinary chat.
- 当前宿主负责调用模型、工具、终端与实际代码修改。
- Super Dev 不是大模型平台，也不提供自己的代码生成 API。
Runtime Contract（强制）
- Super Dev 由两部分组成：
- 当前项目内的本地 Python CLI 工具
- 当前宿主里的规则/Skill/命令映射
- 当前宿主负责调用模型、联网、终端、编辑器与实际代码修改。
- 当用户通过 Codex App/Desktop 的
/super-devskill 入口、Codex CLI 的$super-dev，或super-dev: .../super-dev：...回退入口触发时，都意味着你必须进入 Super Dev 流水线。 - 需要研究、设计、编码、运行、调试时，优先使用 Codex 自身的 web/search/terminal/edit 能力。
- 需要做治理动作时，才使用本地
super-devCLI。
宿主交互边界
普通用户只需要记住 3 个终端命令：
super-dev
super-dev update
super-dev uninstall普通用户优先只记住这些宿主表达：
/super-dev <goal>
/super-dev-seeai <goal>
继续当前流程
现在下一步是什么文本回退宿主优先使用：
super-dev: <goal>
super-dev-seeai: <goal>维护/治理场景才显式进入：
/super-dev-work <mode> <goal>
/super-dev-run <stage|resume|status|next>
/super-dev-review <target> <action>工作模式固定为：
new：从 0 到 1evolve：已有项目增量迭代variant：从现有项目派生新版本patch：在现有项目上修 bug / 做整改resume：继续当前中断流程
硬规则：
new才能直接从research -> docs开始evolve / variant / patch必须先baseline- baseline 必须先分析现有功能、架构、代码、路由/API、UI 与约束，再进入差量 research 和三文档
resume是默认场景，不是异常场景
恢复是默认场景，不是补充场景。优先理解这些表达：
继续当前流程现在下一步是什么/super-dev 继续当前流程
内部 CLI 能力仍可存在，但不应再被当成普通用户主心智。
首轮响应契约（强制）
- 首次触发时第一轮回复必须说明：流水线已激活，当前阶段是
research。 - 先读取
.super-dev/WORKFLOW.md与output/*-bootstrap.md（若存在）。 - 说明固定顺序：research -> 三份核心文档 -> 等待确认 -> Spec/tasks -> 前端优先 -> 后端/测试/交付。
- 三份核心文档完成后暂停等待确认；未经确认不创建 Spec 也不编码。
research 双引擎
引擎 1: 本地知识发现 — 优先读取 knowledge/ 和 knowledge-bundle.json，并在当前宿主里把结论沉入 output/*-research.md。
引擎 2: 宿主联网研究 — WebFetch/WebSearch 搜索同类产品、竞品和官方文档，写入 output/*-research.md。
两个引擎的结果都必须在 PRD/架构/UIUX 文档中被继承。
本地知识库契约（强制）
- 存在
knowledge/时，research 与文档阶段优先读取相关知识文件。 - 存在
output/knowledge-cache/*-knowledge-bundle.json时，先读取 local_knowledge / web_knowledge / research_summary。 - 命中的知识是项目约束（标准/检查清单/反模式/场景包/质量门禁），必须继承到 PRD、架构、UIUX、Spec 和实现阶段。
- 未经用户确认禁止创建
.super-dev/changes/*或开始编码。 - 产物必须真实写入项目文件，不能只在聊天中口头描述。
编码前门禁（Spec 确认后、编码开始前必须执行）
跳过任何一步都会导致大量返工：
第 1 步：技术栈预研（最关键）
- 读取项目依赖文件（package.json / requirements.txt / go.mod 等），找到主要依赖的精确版本号
- 用 WebFetch 查阅每个主要框架的官方文档：Getting Started、Migration Guide、API Reference
- 不确定 API 写法时，先查官方文档再写代码，永远不要猜
第 2 步：读取项目配置
super-dev.yaml确认技术栈选择- 框架配置文件、tsconfig.json、.env.example
- 已有代码目录结构
第 3 步：声明 UI 工具链
- 声明并确认图标库（Lucide/Heroicons/Tabler）和组件库已安装
- 不声明 = 不允许写 UI 代码
第 4 步：确认 API 契约和设计 token
- 读取 output/*-architecture.md 中的 API 定义
- 读取 output/*-uiux.md 中的设计 token
第 5 步：在宿主里建立页面结构与共享类型并验证构建
- 按
output/*-architecture.md与output/*-uiux.md直接在宿主里生成/更新页面结构、组件实现参考与共享类型 - 运行宿主原生构建命令确认零错误后才开始写业务代码
会话连续性契约（强制）
- 若存在
.super-dev/SESSION_BRIEF.md，每次继续前必须先读取。 - 用户在确认门/返工门说"改/补充/确认/继续"等，属于流程内动作，不退回普通聊天。
- 修改后留在当前门里，总结变化并再次等待确认。
- UI 不满意 -> 先更新
output/*-uiux.md，再重做前端 + UI review。 - 架构不合理 -> 先更新
output/*-architecture.md，再调整 Spec/实现。 - 质量不达标 -> 先修复，重新执行 quality gate + proof-pack。
- 启用 policy 时不得默认建议降低治理强度。
实现闭环契约（强制）
- 每轮修改后先做最小 diff review 再汇报完成。
- 运行 build / type-check / test / runtime smoke。
- 新增代码必须接入真实调用链；未接入则删除，禁止留 unused code。
- 新增日志/告警/埋点必须验证会在真实路径触发。
编码阶段持续治理
读取 .super-dev/pipeline-state.json 了解当前在哪个阶段。
根据阶段调整你的工作重点：research 阶段侧重调研，frontend 阶段侧重 UI 实现，quality 阶段侧重测试和门禁。
每次进入新阶段时宣告: Super Dev | [N/9] 阶段名 开始 | 主导专家: XXX
每次写文件前自检
- "use client" 是否需要？（Next.js）
- 图标来自声明的图标库？（不是 emoji）
- 颜色来自设计 token？（不是硬编码 hex）
- import 路径正确？API 路径与架构文档一致？
每完成一个功能后
- build 无错误 2. lint 无 error 3. 无控制台红色错误
- 对比 output/*-uiux.md 视觉一致 5. 运行 validate-superdev.sh（如有）
Show full SKILL.md (339 more words)Show less
Required behavior
- First reply: say Super Dev pipeline mode is active and the current phase is
research. - Before the first reply, read
.super-dev/WORKFLOW.mdandoutput/*-bootstrap.mdwhen present and treat them as the explicit bootstrap contract for this repository. - Read
knowledge/andoutput/knowledge-cache/*-knowledge-bundle.jsonwhen present. - Use Codex native web/search/edit/terminal capabilities to produce:
output/*-research.mdoutput/*-prd.mdoutput/*-architecture.mdoutput/*-uiux.md
- Write the required artifacts into the repository workspace. Chat-only summaries do not count as completion.
- Stop after the three core documents and wait for explicit confirmation.
- Only after confirmation, create
.super-dev/changes/*/proposal.mdand.super-dev/changes/*/tasks.md, then continue with frontend-first implementation. - If the user says the UI is unsatisfactory, requests a redesign, or says the page looks AI-generated, first update
output/*-uiux.md, then redo the frontend, rerun frontend runtime and UI review, and only then continue. - If the user says the architecture is wrong or the technical plan must change, first update
output/*-architecture.md, then realign Spec/tasks and implementation before continuing. - If the user says quality or security is not acceptable, first fix the issues, rerun the quality gate, refresh any delivery evidence the reports ask for, and only then continue.
Never do this
- Never jump straight into coding after
super-dev:orsuper-dev：. - Never create Spec or implementation work before the documents are confirmed.
- 未经用户明确确认，禁止创建
.super-dev/changes/*。 - Use local
super-devCLI for governance actions only; keep research, drafting, coding, and debugging inside Codex.
宿主常犯错误速查（每次编码前扫一眼）
错误 1: 使用 emoji 作为图标
// ❌ <button>🔍 搜索</button>
// ✅ import { Search } from 'lucide-react'
// <button><Search size={16} /> 搜索</button>错误 2: 紫色渐变 AI 模板
// ❌ bg-gradient-to-r from-purple-500 to-pink-500
// ✅ 使用 output/*-uiux.md 定义的品牌色: bg-primary + text-heading-1错误 3: 前后端 API 路径不一致
// ❌ 架构文档写 /api/users，后端实际是 /api/v1/users
// ✅ 编码前先确认 output/*-architecture.md 中的 API 路径错误恢复策略
遇到错误时按以下优先级恢复：
阶段 1 -- 便宜恢复（不丢失上下文）
- Token 超限？注入"继续，不要回顾"然后重试
- 工具失败？注入错误详情 + 备选方案，继续
- 权限拒绝？说明允许什么，继续
阶段 2 -- 上下文重建（可能丢失细节）
- Prompt 过长？压缩旧上下文，保留最近内容
- 多次失败？丢弃非关键历史，只保留关键决策
阶段 3 -- 暴露错误（无法恢复）
- 提供: 什么失败了 + 为什么 + 下一步建议
- 回到终端重新运行
super-dev校验宿主接入；若本地版本或注入面不一致，再执行super-dev update
永远不要在尝试阶段 1-2 之前就暴露错误给用户。
Agent Teams 协作（支持 Teams 功能的宿主）
如果宿主支持 Agent Teams（如 Claude Code 的 /teams），可以让多位 Super Dev 专家并行工作：
研究阶段: PM + ARCHITECT 并行调研 文档阶段: PRD / Architecture / UIUX 可并行起草 编码阶段: 前端 + 后端可并行开发（注意 API 契约对齐） 质量阶段: Security + QA + Performance 并行审查
使用 Teams 时的约束：
- 每个 teammate 必须声明自己的专家角色
- teammates 之间通过共享文件（output/*.md）传递上下文
- 修改同一文件前必须协调（避免冲突）
- 质量门禁结果必须等所有 teammates 完成后汇总
Super Dev System Flow Contract
- SUPER_DEV_FLOW_CONTRACT_V1
- PHASE_CHAIN: research>docs>docs_confirm>spec>frontend>preview_confirm>backend>quality>delivery
- DOC_CONFIRM_GATE: required
- PREVIEW_CONFIRM_GATE: required
- HOST_PARITY: required
© shangyankeji, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/super-dev of shangyankeji/super-dev.
Open the folder on GitHubat commit d06e640
Compare with similar skills
Super Dev 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Super Dev this skillshangyankeji/super-dev | 273 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Bugsfossasia/eventyay-interpretation | 1.6k | 32 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
More from shangyankeji/super-dev
Super Dev
shangyankeji/super-dev
Super Dev pipeline governance for research-first, commercial-grade AI coding delivery
Super Dev Seeai
shangyankeji/super-dev
Activate the Super Dev SEEAI competition mode inside Codex CLI.
Super Dev
shangyankeji/super-dev
Super Dev Codex App/Desktop plugin entry. An agent skill from shangyankeji/super-dev.
Super Dev Seeai
shangyankeji/super-dev
Super Dev SEEAI Codex App/Desktop competition entry. An agent skill from shangyankeji/super-dev.
Related
Categories
Questions about Super Dev
What does Super Dev do?
Activate the Super Dev pipeline inside Codex CLI. An agent skill from shangyankeji/super-dev. Super Dev is an agent skill from shangyankeji/super-dev. Activate the Super Dev pipeline inside Codex CLI.
When should I use Super Dev?
Super Dev fits situations like: testing & QA work in your project.
How do I install Super Dev in Claude Code?
Run `npx skills add shangyankeji/super-dev --skill super-dev -a claude-code`. Or copy the skill folder (.agents/skills/super-dev in shangyankeji/super-dev) into .claude/skills/super-dev in your project. Claude Code loads it when a task matches its description.
How do I install Super Dev in Codex?
Run `npx skills add shangyankeji/super-dev --skill super-dev -a codex`. Or copy the skill folder (.agents/skills/super-dev in shangyankeji/super-dev) into .agents/skills/super-dev in your project. Codex loads it when a task matches its description.
Can I use Super Dev 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 shangyankeji/super-dev --skill super-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/super-dev, .gemini/skills/super-dev, .github/skills/super-dev and .opencode/skills/super-dev in your project.
What does Super Dev need to run?
SKILL.md names no scripts, command-line tools or credentials: Super Dev is instructions for the agent only. Our summary lists: Python 3.
Does Super Dev access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Super Dev 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 Super Dev use?
Super Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Super Dev use?
About 2.1k tokens (SKILL.md is roughly 8.4k 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 Super Dev?
Skills that share tags, products or a category with Super Dev: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Super Dev?
shangyankeji (a GitHub user) maintains it in shangyankeji/super-dev, which has 273 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 19, 2026.
Source: shangyankeji/super-dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.