all publishers

tyrchen

@tyrchen source repo

33 published skills

  1. ▌
    Impl 6 · tyrchen bundle
    Polish and expand the relevant feature specs first, then implement one phase of the project impl plan end-to-end with high quality bars (correctness, elegance, performance), and run an independent code review against the polished specs before declaring done. Use whenever the user says "build phase N", "implement the next phase", "land M0/M1/M2/M3", "follow the impl plan", "ship phase X entirely", "based on specs think ultra hard and build phase X", or asks for a phase-shaped slice of the spec set. Trigger even when the user does not say "impl" if they reference an impl plan / roadmap milestone and ask Codex to build it.
    4 installs
  2. ▌
    Impl 7 · tyrchen
    Implement one phase of ./specs/91-impl-plan.md end-to-end with high quality bars (correctness, elegance, performance), then run an independent code review against the relevant specs and fix every valid finding before declaring done. Use whenever the user says "build phase N", "implement the next phase", "land M0/M1/M2/M3", "follow the impl plan", "ship phase X entirely", "based on @specs/91-impl-plan.md think ultra hard and build phase X", or asks for a phase-shaped slice of the spec set. Trigger even when the user does not say "impl" if they reference an impl plan / roadmap milestone and ask Claude to build it.
    4 installs
  3. ▌
    Spec 7 · tyrchen
    Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs — PRD, component designs, glossary, security/perf/test cross-cuts, key-decisions log, stakeholder roadmap, and engineer-facing implementation plan — cross-referenced with prior-art memos in ./docs/research and vendored code in ./vendors. Use whenever the user says "write the spec", "design this", "let's plan X", "produce a PRD / impl plan / roadmap", "restructure the specs", "review and re-organise the design", "think ultra hard and split this into phases", or describes a non-trivial system that needs a written design before code. Trigger even when the user does not say "spec" if they ask for phased delivery, milestone exit criteria, or a build-order graph.
    2 installs
  4. ▌
    Research 6 · tyrchen
    Vendor reference repos as git submodules under ./vendors and produce deep research memos under ./docs/research covering architecture, design, key data structures, and load-bearing algorithms. Use whenever the user asks to research, study prior art, spike an assumption, compare upstream repos, or learn from pasted GitHub URLs before design or implementation.
    2 installs
  5. ▌
    Impl 4 · tyrchen bundle
    Implement one phase of ./specs/91-impl-plan.md end-to-end with high quality bars (correctness, elegance, performance), then run an independent code review against the relevant specs and fix every valid finding before declaring done. Use whenever the user says "build phase N", "implement the next phase", "land M0/M1/M2/M3", "follow the impl plan", "ship phase X entirely", "based on @specs/91-impl-plan.md think ultra hard and build phase X", or asks for a phase-shaped slice of the spec set. Trigger even when the user does not say "impl" if they reference an impl plan / roadmap milestone and ask Codex to build it.
    5 installs
  6. ▌
    Spec 5 · tyrchen bundle
    Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs — PRD, component designs, glossary, security/perf/test cross-cuts, key-decisions log, stakeholder roadmap, and engineer-facing implementation plan — cross-referenced with prior-art memos in ./docs/research and vendored code in ./vendors. Use whenever the user says "write the spec", "design this", "let's plan X", "produce a PRD / impl plan / roadmap", "restructure the specs", "review and re-organise the design", "think ultra hard and split this into phases", or describes a non-trivial system that needs a written design before code. Trigger even when the user does not say "spec" if they ask for phased delivery, milestone exit criteria, or a build-order graph.
    2 installs
  7. ▌
    Impl 5 · tyrchen
    Implement one phase of ./specs/91-impl-plan.md end-to-end with high quality bars (correctness, elegance, performance), then run an independent code review against the relevant specs and fix every valid finding before declaring done. Use whenever the user says "build phase N", "implement the next phase", "land M0/M1/M2/M3", "follow the impl plan", "ship phase X entirely", "based on @specs/91-impl-plan.md think ultra hard and build phase X", or asks for a phase-shaped slice of the spec set. Trigger even when the user does not say "impl" if they reference an impl plan / roadmap milestone and ask Claude to build it.
    5 installs
  8. ▌
    Spec 6 · tyrchen
    Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs — PRD, component designs, glossary, security/perf/test cross-cuts, key-decisions log, stakeholder roadmap, and engineer-facing implementation plan — cross-referenced with prior-art memos in ./docs/research and vendored code in ./vendors. Use whenever the user says "write the spec", "design this", "let's plan X", "produce a PRD / impl plan / roadmap", "restructure the specs", "review and re-organise the design", "think ultra hard and split this into phases", or describes a non-trivial system that needs a written design before code. Trigger even when the user does not say "spec" if they ask for phased delivery, milestone exit criteria, or a build-order graph.
    3 installs
  9. ▌
    Research 5 · tyrchen bundle
    Vendor reference repos as git submodules under ./vendors and produce deep research memos under ./docs/research covering architecture, design, key data structures, and load-bearing algorithms. Use whenever the user says "do research on X", "study how Y works", "submodule this repo and look into it", "understand the design of Z before we start", "spike on …", references prior-art crates / repos that should be evaluated, or asks to refer to ./vendors before designing or implementing. Trigger even when the user does not say the word "research" if they paste GitHub URLs and ask Codex to learn from them, compare alternatives, or extract patterns.
    6 installs
  10. ▌
    Research 4 · tyrchen
    Vendor reference repos as git submodules under ./vendors and produce deep research memos under ./docs/research covering architecture, design, key data structures, and load-bearing algorithms. Use whenever the user says "do research on X", "study how Y works", "submodule this repo and look into it", "understand the design of Z before we start", "spike on …", references prior-art crates / repos that should be evaluated, or asks to refer to ./vendors before designing or implementing. Trigger even when the user does not say the word "research" if they paste GitHub URLs and ask Claude to learn from them, compare alternatives, or extract patterns.
    2 installs
  11. ▌
    Spec 3 · tyrchen bundle
    Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs — PRD, component designs, glossary, security/perf/test cross-cuts, key-decisions log, stakeholder roadmap, and engineer-facing implementation plan — cross-referenced with prior-art memos in ./docs/research and vendored code in ./vendors. Use whenever the user says "write the spec", "design this", "let's plan X", "produce a PRD / impl plan / roadmap", "restructure the specs", "review and re-organise the design", "think ultra hard and split this into phases", or describes a non-trivial system that needs a written design before code. Trigger even when the user does not say "spec" if they ask for phased delivery, milestone exit criteria, or a build-order graph.
    6 installs
  12. ▌
    Impl 3 · tyrchen
    Implement one phase of ./specs/91-impl-plan.md end-to-end with high quality bars (correctness, elegance, performance), then run an independent code review against the relevant specs and fix every valid finding before declaring done. Use whenever the user says "build phase N", "implement the next phase", "land M0/M1/M2/M3", "follow the impl plan", "ship phase X entirely", "based on @specs/91-impl-plan.md think ultra hard and build phase X", or asks for a phase-shaped slice of the spec set. Trigger even when the user does not say "impl" if they reference an impl plan / roadmap milestone and ask Claude to build it.
    4 installs
  13. ▌
    Spec 4 · tyrchen
    Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs — PRD, component designs, glossary, security/perf/test cross-cuts, key-decisions log, stakeholder roadmap, and engineer-facing implementation plan — cross-referenced with prior-art memos in ./docs/research and vendored code in ./vendors. Use whenever the user says "write the spec", "design this", "let's plan X", "produce a PRD / impl plan / roadmap", "restructure the specs", "review and re-organise the design", "think ultra hard and split this into phases", or describes a non-trivial system that needs a written design before code. Trigger even when the user does not say "spec" if they ask for phased delivery, milestone exit criteria, or a build-order graph.
    6 installs
  14. ▌
    Research 3 · tyrchen bundle
    Vendor reference repos as git submodules under ./vendors and produce deep research memos under ./docs/research covering architecture, design, key data structures, and load-bearing algorithms. Use whenever the user says "do research on X", "study how Y works", "submodule this repo and look into it", "understand the design of Z before we start", "spike on …", references prior-art crates / repos that should be evaluated, or asks to refer to ./vendors before designing or implementing. Trigger even when the user does not say the word "research" if they paste GitHub URLs and ask Claude to learn from them, compare alternatives, or extract patterns.
    2 installs
  15. ▌
    Impl 2 · tyrchen
    Implement one phase of ./specs/91-impl-plan.md end-to-end with high quality bars (correctness, elegance, performance), then run an independent code review against the relevant specs and fix every valid finding before declaring done. Use whenever the user says "build phase N", "implement the next phase", "land M0/M1/M2/M3", "follow the impl plan", "ship phase X entirely", "based on @specs/91-impl-plan.md think ultra hard and build phase X", or asks for a phase-shaped slice of the spec set. Trigger even when the user does not say "impl" if they reference an impl plan / roadmap milestone and ask Claude to build it.
    3 installs
  16. ▌
    Spec 2 · tyrchen
    Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs — PRD, component designs, glossary, security/perf/test cross-cuts, key-decisions log, stakeholder roadmap, and engineer-facing implementation plan — cross-referenced with prior-art memos in ./docs/research and vendored code in ./vendors. Use whenever the user says "write the spec", "design this", "let's plan X", "produce a PRD / impl plan / roadmap", "restructure the specs", "review and re-organise the design", "think ultra hard and split this into phases", or describes a non-trivial system that needs a written design before code. Trigger even when the user does not say "spec" if they ask for phased delivery, milestone exit criteria, or a build-order graph.
    3 installs
  17. ▌
    Research 2 · tyrchen
    Vendor reference repos as git submodules under ./vendors and produce deep research memos under ./docs/research covering architecture, design, key data structures, and load-bearing algorithms. Use whenever the user says "do research on X", "study how Y works", "submodule this repo and look into it", "understand the design of Z before we start", "spike on …", references prior-art crates / repos that should be evaluated, or asks to refer to ./vendors before designing or implementing. Trigger even when the user does not say the word "research" if they paste GitHub URLs and ask Claude to learn from them, compare alternatives, or extract patterns.
    4 installs
  18. ▌
    Repoctl 2 · tyrchen bundle
    Use repoctl as the source of truth for monorepo graph, affected, CI, context, and task workflows.
    6 installs
  19. ▌
    Pr Review 2 · tyrchen bundle
    Summarize PR impact using repoctl affected data, risk flags, and graph diagnostics.
    2 installs
  20. ▌
    App Creation 2 · tyrchen bundle
    Create new apps, frameworks, and foundation services with repoctl templates and manifests.
    4 installs
  21. ▌
    Proto Change 2 · tyrchen bundle
    Change source proto contracts through owners and never edit generated code directly.
    3 installs
  22. ▌
    Monorepo Boundaries 2 · tyrchen bundle
    Respect app, framework, foundation, proto, generated-code, and IaC boundaries.
    4 installs
  23. ▌
    Build High Quality Slides · tyrchen bundle
    Design, build, revise, and validate high-quality slide decks and modern HTML slide sites. Use when Codex needs to turn an outline into a presentation, improve an existing deck, remove AI-like or translated prose, design diagrams and D3 visualizations, add transitions and keyboard/fullscreen behavior, separate slide content from styles, audit title wrapping and overflow, or publish a static presentation to GitHub Pages. Especially useful for long Chinese technical talks with multiple topics, demos, charts, and a narrative ending.
    2 installs
  24. ▌
    Impl · tyrchen bundle
    Implement one phase of ./specs/91-impl-plan.md end-to-end with high quality bars (correctness, elegance, performance), then run an independent code review against the relevant specs and fix every valid finding before declaring done. Use whenever the user says "build phase N", "implement the next phase", "land M0/M1/M2/M3", "follow the impl plan", "ship phase X entirely", "based on @specs/91-impl-plan.md think ultra hard and build phase X", or asks for a phase-shaped slice of the spec set. Trigger even when the user does not say "impl" if they reference an impl plan / roadmap milestone and ask Codex to build it.
    3 installs
  25. ▌
    Spec · tyrchen bundle
    Turn a feature idea or rough requirement into a complete, dependency-ordered spec set under ./specs — PRD, component designs, glossary, security/perf/test cross-cuts, key-decisions log, stakeholder roadmap, and engineer-facing implementation plan — cross-referenced with prior-art memos in ./docs/research and vendored code in ./vendors. Use whenever the user says "write the spec", "design this", "let's plan X", "produce a PRD / impl plan / roadmap", "restructure the specs", "review and re-organise the design", "think ultra hard and split this into phases", or describes a non-trivial system that needs a written design before code. Trigger even when the user does not say "spec" if they ask for phased delivery, milestone exit criteria, or a build-order graph.
    2 installs
  26. ▌
    Research · tyrchen bundle
    Vendor reference repos as git submodules under ./vendors and produce deep research memos under ./docs/research covering architecture, design, key data structures, and load-bearing algorithms. Use whenever the user says "do research on X", "study how Y works", "submodule this repo and look into it", "understand the design of Z before we start", "spike on …", references prior-art crates / repos that should be evaluated, or asks to refer to ./vendors before designing or implementing. Trigger even when the user does not say the word "research" if they paste GitHub URLs and ask Codex to learn from them, compare alternatives, or extract patterns.
    6 installs
  27. ▌
    Repoctl · tyrchen bundle
    Use repoctl as the source of truth for monorepo graph, affected, CI, context, and task workflows.
    4 installs
  28. ▌
    Pr Review · tyrchen bundle
    Summarize PR impact using repoctl affected data, risk flags, and graph diagnostics.
    3 installs
  29. ▌
    App Creation · tyrchen bundle
    Create new apps, frameworks, and foundation services with repoctl templates and manifests.
    4 installs
  30. ▌
    Proto Change · tyrchen bundle
    Change source proto contracts through owners and never edit generated code directly.
    4 installs
  31. ▌
    Monorepo Boundaries · tyrchen bundle
    Respect app, framework, foundation, proto, generated-code, and IaC boundaries.
    4 installs
  32. ▌
    Design Guide · tyrchen bundle
    Extract comprehensive design language from websites including colors, typography, animations, interactive states, shadows, gradients, component patterns, and UX behaviors. Generates pixel-perfect design guides with responsive screenshots and complete design system documentation. Use when analyzing website design, creating design systems, or rebuilding sites.
    1 install
  33. ▌
    Council · tyrchen bundle
    Council · 智囊团:蒸馏真人思维框架为Advisor,并支持多Advisor圆桌讨论。 所有Advisor以persona文件形式存储在 personas/ 目录下,由Council统一管理。 三种用法: (A) 蒸馏:输入人名/主题/模糊需求 → 深度调研 → 提炼心智模型 → 生成Advisor persona (B) 激活:加载已有Advisor,以其视角回答问题 (C) 圆桌:召集多个Advisor → 独立发言 → 交叉质疑 → 综合输出 触发词(蒸馏):「蒸馏XX」「造skill」「做个XX视角」「XX的思维方式」「更新XX的persona」 触发词(激活):「用XX的视角」「XX会怎么看」「XX模式」「切换到XX」「ask XX」 触发词(圆桌):「问问council」「圆桌讨论」「让XX和YY讨论」「ask the council」「council session」 模糊需求也触发:「我想提升决策质量」「有没有一种思维方式能帮我...」「我需要一个思维顾问」
    3 installs