jsonlee12138
- 125 skills
- 0 followers
- 15 hours ago last updated
- ▌ Agent Doctor · jsonlee12138 bundleDiagnose the availability and correctness of custom subagent files across Codex (`.codex/agents/*.toml`), Claude Code (`.claude/agents/*.md`), and Cursor (`.cursor/agents/*.md`). Use when the user asks to check, diagnose, validate, or health-check agents; when a spawned subagent behaves as if it has no instructions; or after creating/editing agent files.
- ▌ Record Issue · jsonlee12138兼容旧的“小需求/小改动记录”调用。用户显式调用 record-issue,或旧提示要求快速建单时使用;将输入归一化到 intake 的统一 Work Item,确认完整问题、原因或限制、方案、影响、范围、验收和测试策略后再记录。新工作优先直接使用自然语言或 intake。
- ▌ Skillos Lite · jsonlee12138 bundleCurate insert/update/deprecate/noop proposals for the VibeRig skill library only when the user explicitly requests a skill-library audit or SkillOS-style curation. Do not run from acceptance, insights, or default self-learning, and never apply changes directly.
- ▌ Split Issues · jsonlee12138把已确认 Work Item 的里程碑拆成可验证垂直 Issue。由 pre-development 内部生成草案,并在需求基线已确认后按 Rolling Wave materialize;不作为人工流程入口,不指派人员或 subagent。
- ▌ Agent Creator · jsonlee12138 bundleCreate or update custom subagent files for Codex (`.codex/agents/*.toml`), Claude Code (`.claude/agents/*.md`), and/or Cursor (`.cursor/agents/*.md`). Use when the user asks to create, design, review, or refine a subagent/custom agent for any of these platforms, define agent task boundaries, choose model/permission settings, add preferred skill dependency guidance, or port an existing subagent to another platform.
- ▌ Skill Builder · jsonlee12138 bundleCreate or update Agent Skills/Codex skills with reliable trigger descriptions, concise SKILL.md workflows, progressive disclosure, reusable scripts/references/assets, and validation checklists. Use when the user asks to design, create, refine, audit, or troubleshoot a skill, SKILL.md file, or reusable agent workflow package.
- ▌ Tech Research · jsonlee12138供 pre-development 与架构流程内部调用的领域技术调研协议,按前端、后端、数据、安全、运维、QA 等使命生成证据化可行性报告。也可在用户明确要求技术调研或 spike 时直接使用;内部模式下 subagent 不写文件、不碰 Linear。
- ▌ Accept Deliver · jsonlee12138 bundle对已完成技术验证的 VibeRig 工作执行证据审计、人工 UAT、明确验收和授权交付。用户说“验收、确认完成、accept、合并已验收 PR、交付、发布”,或旧的 accept-issue、accept-milestone、merge-issue 流程触发时使用。发现问题时返回 execute Goal Loop,不在本 skill 内修代码。
- ▌ Blocker Resume · jsonlee12138兼容旧的 VibeRig 阻塞恢复调用。用户要求恢复、继续、解除 blocker,或提供被阻塞的 Issue、PR、测试日志时使用;读取历史尝试和当前证据,恢复 execute Goal Loop。只有产品决策、权限、不可模拟真实环境或连续三次无进展才向用户请求输入。
- ▌ Prd Brainstorm · jsonlee12138生成产品级 PRD。用户明确要独立做产品脑暴或写 PRD 时采用访谈模式;由 pre-development 调用时采用内部综合模式,根据已确认的 Intake 自动判断范围、用户故事与优先级,不重复询问老板。不创建 Linear Milestone / Issue。
- ▌ Built In Agents · jsonlee12138 bundleInstall or reconcile the VibeRig baseline agent team across Codex, Claude Code, and Cursor from provider-neutral JSON specs. Use from `vb-init`, when baseline agents are missing or outdated, or when the user asks to restore/reconcile bundled agents. Project-specific roles belong to `update-team`.
- ▌ Pre Development · jsonlee12138 bundle为已确认的 L2/L3 Work Item 生成技术调研、架构、AC/TC、风险和交付计划。通常由 intake 在人工需求基线确认后内部调用;用户明确要求架构或开发前方案时也可使用。不用于 L0/L1 固定流程,不新增人工审批阶段,结论改变产品语义时返回 intake。
- ▌ Accept Milestone · jsonlee12138兼容旧的 Milestone 验收调用。用户显式调用 accept-milestone 或要求验收一个里程碑时使用;将聚合范围解析为 accept-deliver 的 milestone 模式,复用有效 Issue Evidence,只补里程碑回归、E2E 与人工 UAT。新工作优先直接使用自然语言或 accept-deliver。
- ▌ Split Milestones · jsonlee12138将已确认 Work Item 按可验收用户价值拆成里程碑,先作为不可执行草案写入 Linear 供人工可视化确认,再在批准后激活。由 pre-development 内部调用;也可用于继续已确认需求的里程碑规划。
- ▌ Subagent Routing · jsonlee12138 bundle在 execute 或 pre-development 已判定需要独立专业能力时,选择 VibeRig research、planning、implementation、QA、review 或 integration Subagent,并按任务族、风险、accepted Evidence、成本和当前模型目录选择 model/reasoning。仅作为内部能力与成本路由使用;不因任务来自 Linear 就自动触发,不让用户手动挑 Skill、Agent 或模型。
- ▌ Define Acceptance · jsonlee12138 bundle把统一 Work Item 与架构转成可判定验收标准、工程验证方式和用户可执行 UAT 指南。通常由 intake 在需求确认前建立基础 oracle,或由 pre-development 在确认后补充技术细节;不新增独立人工阶段。
- ▌ Architecture Design · jsonlee12138由 pre-development 在领域调研后调用的 CTO 架构综合与红白队对抗流程,定稿模块、接口、数据、安全、失败模式、迁移、可观测性和测试性。用户明确要求架构设计时也可直接使用。不创建 Linear Milestone / Issue。
- ▌ Code Simplification · jsonlee12138Use when the user asks to simplify, reduce complexity, or improve readability of existing code without changing behavior. Triggers on "simplify", "too complex", "hard to read", "reduce nesting", "clean up", "make clearer", or "refactor for clarity". Not for bug fixes, feature additions, or performance tuning.
- ▌ Documentation And Adrs · jsonlee12138 bundleCreate or update Architecture Decision Records (ADRs), inline documentation, and API docs. Use when making a significant technical decision, changing a public API, shipping a user-facing feature, onboarding a new agent or team member, or when the codebase lacks a record of why something was built a certain way.
- ▌ Security And Hardening · jsonlee12138 bundleHarden code against vulnerabilities. Use when handling user input, authentication, data storage, external integrations, or LLM/AI features. Use when building anything that accepts untrusted data, manages user sessions, or interacts with third-party services.
- ▌ Test Driven Development · jsonlee12138 bundle在 execute Goal Loop 中用测试驱动新逻辑、行为变化和 Bug 修复,并为缺少配置或依赖的测试自动选择 fake、stub、ephemeral dependency 或 sandbox。文档、纯静态内容或无行为配置不使用。
- ▌ API And Interface Design · jsonlee12138 bundleGuides stable API and interface design. Use when designing REST or GraphQL endpoints, defining TypeScript type contracts, setting module boundaries, or reviewing public interfaces between frontend and backend. Triggers on requests like "design this API", "define the contract for", "create endpoint for", "how should this interface look", or "add pagination to".
- ▌ Source Driven Development · jsonlee12138Ground every implementation decision in official documentation. Use when writing framework-specific code, implementing patterns where version correctness matters, or when the user wants verified, source-cited code. Do not use for version-independent logic, or when the user explicitly wants speed over verification.
- ▌ Incremental Implementation · jsonlee12138Deliver changes in thin vertical slices. Use when implementing any feature or change touching more than one file, or when you're about to write a large amount of code at once. Do not use for single-file, single-function changes with minimal scope.
- ▌ Browser Testing With Devtools · jsonlee12138 bundleUse when debugging or testing a frontend feature in a live browser: inspecting network requests, analyzing console errors, examining DOM state, profiling page performance, or running automated browser checks via Claude in Chrome MCP tools. Key terms: devtools, network tab, console error, DOM inspect, performance profile, browser debug, chrome, XHR, fetch, layout shift, memory leak.