Design a consequential software change across boundaries, data, APIs, deployment, or reliability and record the decision as a lightweight ADR. Use when implementation choices affect long-term structure or migration. Do not use for trivial local edits.
EnglishImplement the smallest end-to-end user-visible behavior using test-driven development and real system boundaries, then return reproducible acceptance evidence. Use after a spec identifies a concrete slice. Do not use for planning-only or review-only work.
EnglishDerive or extend a product design system from real context, producing semantic design tokens, component contracts, states, accessibility rules, and implementation mappings. Use for design-system creation or substantial UI work. Do not use to generate an arbitrary trendy palette.
EnglishTurn an ambiguous software idea into one verified, review-ready vertical slice by composing specification, architecture, planning, TDD implementation, debugging, and review. Use for end-to-end feature delivery or “build this” requests. Do not use for a narrow bug, review-only request, or research-only task.
EnglishDecompose an approved specification into dependency-aware tickets or executable tasks, each delivering a thin vertical outcome with its own proof. Use for implementation planning and ticket tracking. Do not use to invent requirements or replace a missing spec.
EnglishTurn a product brief, screenshot, Figma reference, or existing interface into a coherent design language and visually verified implementation. Use for substantial UI creation or redesign. Do not use for a tiny CSS correction with an existing exact target.
EnglishCreate and verify an interactive UI prototype from a selected visual target or an existing product language. For greenfield work without a target, first generate exactly three different image-based directions and wait for selection. Use for wireframes, prototypes, and UI exploration.
EnglishTurn a source-backed narrative into an editable Xiaohongshu (小红书) carousel with deterministic Chinese typography, safe-area and overflow checks, caption, contact sheet, and export manifest. Use for RedNote social cards. Do not use image models to render Chinese text.
EnglishResearch a topic into a claim ledger with source roles, independence, dates, conflicts, and calibrated confidence. Use when conclusions need current web evidence, including authorized reading from logged-in Chrome pages such as X or Xiaohongshu. Do not use for casual browsing or credential extraction.
EnglishTurn a topic or question into a source-backed publication, optionally an editable Xiaohongshu carousel, by composing claim-led research, synthesis, and deterministic visual production. Use for publishable research or social content. Do not use for a quick factual lookup.
EnglishConvert a rough feature idea, product request, or behavioral change into an implementable specification with examples, non-goals, invariants, interfaces, risks, and a verification plan. Use before planning or coding when the outcome is ambiguous. Do not use when an approved spec already answers these questions.
EnglishIncludes Architect Change, Build Vertical Slice, Design Language, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Architect Change
Design a consequential software change across boundaries, data, APIs, deployment, or reliability and record the decision as a lightweight ADR. Use when implementation choices affect long-term structure or migration. Do not use for trivial local edits.
Build Vertical Slice
Implement the smallest end-to-end user-visible behavior using test-driven development and real system boundaries, then return reproducible acceptance evidence. Use after a spec identifies a concrete slice. Do not use for planning-only or review-only work.
Design Language
Derive or extend a product design system from real context, producing semantic design tokens, component contracts, states, accessibility rules, and implementation mappings. Use for design-system creation or substantial UI work. Do not use to generate an arbitrary trendy palette.
Idea to Production
Turn an ambiguous software idea into one verified, review-ready vertical slice by composing specification, architecture, planning, TDD implementation, debugging, and review. Use for end-to-end feature delivery or “build this” requests. Do not use for a narrow bug, review-only request, or research-only task.
Map Work
Decompose an approved specification into dependency-aware tickets or executable tasks, each delivering a thin vertical outcome with its own proof. Use for implementation planning and ticket tracking. Do not use to invent requirements or replace a missing spec.
Pixels to Product
Turn a product brief, screenshot, Figma reference, or existing interface into a coherent design language and visually verified implementation. Use for substantial UI creation or redesign. Do not use for a tiny CSS correction with an existing exact target.
Prototype Interface
Create and verify an interactive UI prototype from a selected visual target or an existing product language. For greenfield work without a target, first generate exactly three different image-based directions and wait for selection. Use for wireframes, prototypes, and UI exploration.
Rednote Carousel
Turn a source-backed narrative into an editable Xiaohongshu (小红书) carousel with deterministic Chinese typography, safe-area and overflow checks, caption, contact sheet, and export manifest. Use for RedNote social cards. Do not use image models to render Chinese text.
Research Claims
Research a topic into a claim ledger with source roles, independence, dates, conflicts, and calibrated confidence. Use when conclusions need current web evidence, including authorized reading from logged-in Chrome pages such as X or Xiaohongshu. Do not use for casual browsing or credential extraction.
Research to Publication
Turn a topic or question into a source-backed publication, optionally an editable Xiaohongshu carousel, by composing claim-led research, synthesis, and deterministic visual production. Use for publishable research or social content. Do not use for a quick factual lookup.
Shape Spec
Convert a rough feature idea, product request, or behavioral change into an implementable specification with examples, non-goals, invariants, interfaces, risks, and a verification plan. Use before planning or coding when the outcome is ambiguous. Do not use when an approved spec already answers these questions.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Architect Change skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: Apache-2.0. The author’s terms apply.