Agent skill

Developer Experience Architecture

by devcodex-labs in devcodex-labs/devcodex

开发者体验架构专家 Owner — 当任务涉及 CLI、SDK、API、Hook、插件、框架、README、quick start、示例、错误信息、迁移、贡献路径或开发者接入体验时使用;要求验证第一次成功路径、真实示例、错误恢复和维护者消费链。

AGPL-3.0Auto-check passedDevelopment

Install Developer Experience Architecture

skills CLI
$ npx skills add devcodex-labs/devcodex --skill developer-experience-architecture -a claude-code

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

GitHub CLI
$ gh skill install devcodex-labs/devcodex developer-experience-architecture --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/devcodex-labs/devcodex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/content/skills/developer-experience-architecture .claude/skills/developer-experience-architecture && 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
developer-experience-architecture
GitHub stars
439
Token cost
~897 tokens
SKILL.md length
190 words
Files
2
Skills in repo
70
Repo updated
First seen
Licence
AGPL-3.0

At a glance

开发者体验架构专家 Owner — 当任务涉及 CLI、SDK、API、Hook、插件、框架、README、quick start、示例、错误信息、迁移、贡献路径或开发者接入体验时使用;要求验证第一次成功路径、真实示例、错误恢复和维护者消费链。

  • Works in 8 steps: 明确开发者画像:新用户、现有维护者、集成方、插件作者、框架消费者或发布方。 → 跑通或推导 first success… → 检查集成步骤是否依赖本机绝对路径、私有工作区、隐藏文档或未声明前置条件。 → …
  • Development work in your project
  • SKILL.md covers 定位, 触发条件, 核心门禁 and 执行步骤, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Developer Experience Architecture is an agent skill from devcodex-labs/devcodex. 开发者体验架构专家 Owner — 当任务涉及 CLI、SDK、API、Hook、插件、框架、README、quick start、示例、错误信息、迁移、贡献路径或开发者接入体验时使用;要求验证第一次成功路径、真实示例、错误恢复和维护者消费链。

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `intent.json`).

It sits in Development. The repository describes itself as: Intent-driven AI coding workflow runtime for consistent context, skills, approvals, validation, and handoffs across six AI coding hosts. The licence is AGPL-3.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “/developer-experience-architecture”

Workflow steps

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

  1. 明确开发者画像:新用户、现有维护者、集成方、插件作者、框架消费者或发布方。
  2. 跑通或推导 first success path:安装、配置、最小命令、示例输入、成功输出。
  3. 检查集成步骤是否依赖本机绝对路径、私有工作区、隐藏文档或未声明前置条件。
  4. 审查示例:是否符合生产推荐路径、是否说明 fixture/mock/demo 边界。
  5. 审查错误体验:失败时是否可定位、可恢复、可继续验证。
  6. 若 CLI 提供 --json,验证 stdout 只有一个可解析 JSON 文档;合同错误 exit=2、运行检查失败 exit=1、成功 exit=0,默认人读输出不得被 JSON 字段泄漏污染。
  7. 执行 ConfigurationErgonomicsGate:为最高频任务给出最小配置,逐字段证明必要性,冻结复杂度预算,分离高级能力,并验证可选字段真实省略后仍能完成任务。
  8. 对版本或契约变化补迁移路径、兼容策略和文档入口。

What it can do on your machine

Read from SKILL.md and the folder at commit 1dd4525. 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 markdown).

    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

Developer Experience Architecture loads about 897 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 190 words of instructions outside code blocks.

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

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 devcodex-labs/devcodex at commit 1dd4525, republished under its AGPL-3.0 licence (© devcodex-labs). 190 words, ~897 tokens.

Download SKILL.mdSave it as .claude/skills/developer-experience-architecture/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
developer-experience-architecture
description
开发者体验架构专家 Owner — 当任务涉及 CLI、SDK、API、Hook、插件、框架、README、quick start、示例、错误信息、迁移、贡献路径或开发者接入体验时使用;要求验证第一次成功路径、真实示例、错误恢复和维护者消费链。

Developer Experience Architecture Skill

定位

本 Skill 负责开发者体验 Owner 视角。它确保面向开发者的产品、库、插件、CLI、API、Hook、文档和示例不是“内部能懂”,而是让目标开发者能快速接入、正确使用、遇错可恢复、升级可迁移。

触发条件

场景是否触发
CLI / SDK / API / Hook / 插件 / 框架能力变更必须
README、quick start、接入手册、示例、fixture 或文档站面向开发者必须
错误信息、配置项、迁移指南、贡献流程、调试方式会影响开发者必须
纯 UI 视觉或后端内部实现,且没有开发者消费面N/A + skipReason

核心门禁

Gate要求证据
DeveloperExperienceArchitectureGate设计必须覆盖开发者首次成功、集成步骤、错误恢复和升级迁移quick start、示例、命令、错误输出、迁移文档
FirstSuccessPathGate用户按文档从空状态到第一个成功结果的路径必须可执行命令、输入、期望输出、耗时
ExampleTruthGate示例必须是真实业务工作流,不用硬编码单例冒充主路径源码、测试、运行结果、fixtureBoundary
ErrorExperienceGate错误信息必须能指向原因、修复动作和相关文档stderr、日志、排错章节
MachineReadableCliContractGate新增机器可读 CLI 时必须保持默认人读路径,并冻结单一 JSON envelope、稳定错误码、nextStep 与 native exit codehuman/json replay、negative fixture、exit map
MigrationPathGateBreaking 或行为变化必须提供迁移步骤和兼容边界changelog、migration、compat notes
ConfigurationErgonomicsGate配置设计必须让常见任务保持最小、可理解、可省略,复杂度只留在高级能力边界MinimalTaskConfig、FieldNecessityMatrix、ComplexityBudget、AdvancedCapabilityBoundary、OptionalFieldOmissionProbe

执行步骤

  1. 明确开发者画像:新用户、现有维护者、集成方、插件作者、框架消费者或发布方。
  2. 跑通或推导 first success path:安装、配置、最小命令、示例输入、成功输出。
  3. 检查集成步骤是否依赖本机绝对路径、私有工作区、隐藏文档或未声明前置条件。
  4. 审查示例:是否符合生产推荐路径、是否说明 fixture/mock/demo 边界。
  5. 审查错误体验:失败时是否可定位、可恢复、可继续验证。
  6. 若 CLI 提供 --json,验证 stdout 只有一个可解析 JSON 文档;合同错误 exit=2、运行检查失败 exit=1、成功 exit=0,默认人读输出不得被 JSON 字段泄漏污染。
  7. 执行 ConfigurationErgonomicsGate:为最高频任务给出最小配置,逐字段证明必要性,冻结复杂度预算,分离高级能力,并验证可选字段真实省略后仍能完成任务。
  8. 对版本或契约变化补迁移路径、兼容策略和文档入口。

ConfigurationErgonomicsGate

产物要求
MinimalTaskConfig从空状态完成最高频任务所需的最小字段、默认值和成功结果
FieldNecessityMatrix每个公开字段的用户任务、必填理由、默认/推导来源、错误语义和移除影响
ComplexityBudget首次成功所需字段数、嵌套深度、概念数和额外步骤预算;超预算必须有真实消费者证据
AdvancedCapabilityBoundary高级、安全、性能、企业或 provider 特有能力与主路径分离,不污染最小配置
OptionalFieldOmissionProbe删除所有可选字段后运行等价命令 / API / 示例,验证默认路径、错误和文档承诺一致

可推导、可默认、只服务内部实现或只为未来扩展预留的字段不得默认公开为必填。字段数量本身不是唯一指标,但“每个字段都有实现用途”也不能替代用户任务价值证明。

输出字段

markdown
## DeveloperExperienceArchitectureGate

| 字段 | 内容 |
|------|------|
| developerPersona | 目标开发者画像和前置能力 |
| firstSuccessPath | 从空状态到第一个成功结果的步骤、命令和期望输出 |
| integrationSteps | 接入步骤、配置、依赖和环境要求 |
| exampleTruth | 示例是否真实业务工作流;fixture/mock/demo 边界 |
| errorExperience | 常见失败、错误信息、排错入口和恢复动作 |
| machineReadableCli | human/json 兼容、envelope、errorCode/nextStep、exit map 与 spawn 证据 |
| migrationPath | 版本变化、兼容策略、迁移步骤 |
| configurationErgonomics | 最小配置、字段必要性、复杂度预算、高级边界和省略探针 |
| docsEntryPoints | README / 文档站 / API / changelog / examples 可点击入口 |

反模式

反模式修正
quick start 只展示硬编码 happy path补真实业务输入、失败路径和恢复方式
示例文件能跑但不是推荐接入方式标注 exampleTruth / fixtureBoundary,并给生产主路径
错误信息只说 failed输出原因、下一步和文档入口
JSON 模式混入 banner/progress 文本或仍以 exit 0 报错stdout 只输出 envelope,并按合同/检查失败映射 native exit code
文档链接写死本机路径或 .devcodex 私有路径改为仓库相对路径、公开 URL 或说明不可分享边界
把所有底层能力都暴露为配置保留 MinimalTaskConfig,把低频/高级能力放入显式 advanced boundary

与其他 Skill 的关系

  • expert-output-quality:示例和 fixture 必须区分生产推荐路径与验证边界。
  • readme-authoring / user-manual-authoring:README 与接入手册需采用 first success path。
  • release-verification:发布前必须验证 package / install / smoke 对开发者可用。
  • test-router:把 DX 验证映射为 command smoke、pack、example、docs link 和 migration probe。

© devcodex-labs, AGPL-3.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 content/skills/developer-experience-architecture of devcodex-labs/devcodex.

  • SKILL.md
  • intent.json

Open the folder on GitHubat commit 1dd4525

Compare with similar skills

Developer Experience Architecture 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.

Developer Experience Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Developer Experience Architecture this skilldevcodex-labs/devcodex439—~897Automated safety check: PassAGPL-3.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 24 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from devcodex-labs/devcodex

All 70 skills in this repo
  • Accessibility I18n

    devcodex-labs/devcodex

    无障碍与国际化专家 Owner — 当任务涉及可访问性、键盘操作、焦点、屏幕阅读器、ARIA、语言地区、本地化、RTL、翻译资源、用户可见文案或多语言文档时使用;要求把包容性体验和本地化验证绑定到真实用户路径。

    439 GitHub stars~718 tokensUpdated 20 days ago
    Auto-check passed
  • AI Agent System Architecture

    devcodex-labs/devcodex

    AI Agent 系统架构专家 Owner — 当任务涉及 Agent 路由、工具调用、上下文管理、记忆、状态机、权限、人机协作、可观测性、回放验证或模型辅助治理时使用;要求把 Agent 行为设计成可解释、可恢复、可审计。

    439 GitHub stars~2.4k tokensUpdated 20 days ago
    Auto-check passed
  • API Contract Architecture

    devcodex-labs/devcodex

    API 契约架构专家 Owner — 当任务涉及 public API、HTTP/SDK/CLI 契约、版本兼容、错误模型、分页过滤、幂等、Schema、类型、迁移或消费者影响时使用;要求先冻结消费者契约,再设计实现与验证。

    439 GitHub stars~865 tokensUpdated 20 days ago
    Auto-check passed
  • Architecture Design

    devcodex-labs/devcodex

    架构设计文档编排 Owner — 当用户要求架构设计、系统设计、技术架构或可指导开发、Review 与任务拆分的完整方案时使用;要求从业务流程反推节点、状态、数据、一致性、异常补偿、ADR 与实施任务。

    439 GitHub stars~1.1k tokensUpdated 20 days ago
    Auto-check passed
  • Audit Common

    devcodex-labs/devcodex

    审查公共维度 G0~G5 + Profile Freshness Check — 所有 audit 子类型必先执行的基础维度层

    439 GitHub stars~4.1k tokensUpdated 20 days ago
    Auto-check passed
  • Audit Session

    devcodex-labs/devcodex

    审计工作流的跨会话状态机 — 在 <audit-root/.audit-state/<session-id.json 持久化轮次/发现项/收敛状态,支持 Token 中断后精准恢复

    439 GitHub stars~1.8k tokensUpdated 20 days ago
    Auto-check passed

Categories

Questions about Developer Experience Architecture

What does Developer Experience Architecture do?

开发者体验架构专家 Owner — 当任务涉及 CLI、SDK、API、Hook、插件、框架、README、quick start、示例、错误信息、迁移、贡献路径或开发者接入体验时使用;要求验证第一次成功路径、真实示例、错误恢复和维护者消费链。. Developer Experience Architecture is an agent skill from devcodex-labs/devcodex.

When should I use Developer Experience Architecture?

Developer Experience Architecture fits situations like: development work in your project.

How do I install Developer Experience Architecture in Claude Code?

Run `npx skills add devcodex-labs/devcodex --skill developer-experience-architecture -a claude-code`. Or copy the skill folder (content/skills/developer-experience-architecture in devcodex-labs/devcodex) into .claude/skills/developer-experience-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Developer Experience Architecture in Codex?

Run `npx skills add devcodex-labs/devcodex --skill developer-experience-architecture -a codex`. Or copy the skill folder (content/skills/developer-experience-architecture in devcodex-labs/devcodex) into .agents/skills/developer-experience-architecture in your project. Codex loads it when a task matches its description.

Can I use Developer Experience Architecture 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 devcodex-labs/devcodex --skill developer-experience-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developer-experience-architecture, .gemini/skills/developer-experience-architecture, .github/skills/developer-experience-architecture and .opencode/skills/developer-experience-architecture in your project.

What does Developer Experience Architecture need to run?

SKILL.md names no scripts, command-line tools or credentials: Developer Experience Architecture is instructions for the agent only.

Does Developer Experience Architecture 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 Developer Experience Architecture 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 Developer Experience Architecture use?

Developer Experience Architecture is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Developer Experience Architecture use?

About 897 tokens (SKILL.md is roughly 3.6k 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 Developer Experience Architecture?

Skills that share tags, products or a category with Developer Experience Architecture: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Developer Experience Architecture?

devcodex-labs (a GitHub organization) maintains it in devcodex-labs/devcodex, which has 439 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on September 17, 2026.

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