atlas

Create, update, or finalize a note in the kolu Atlas (docs/atlas) — frontmatter, the MDX component kit, build + check-sync, and the preview/share links. Use whenever authoring or editing an Atlas note (e.g. a /be plan-of-record).

Ir para a instalação

Repositório: juspay/kolu
Última atividade na origem: 8 de agosto de 2026 às 14:06
Idioma detectado do SKILL.md: inglês
Estrelas: 78
Forks: 12

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/juspay/kolu --skill atlas

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

Prose in markdown; the component kit (docs/atlas/src/components/ — <Cite>, <Callout>, <PrLink>, <Footnote>, <Terminal>, <AtlasMockup>, <Svg>, <D2>, …) only where markdown can't.
Push asides into <Footnote>, not parentheticals — caveats, citations, "why we rejected X". It renders as a superscript with a popover (full MDX body). Not for load-bearing claims (inline) or whole paragraphs (### or <Callout>).
Every phased work item carries an Atlas-unique identifier — a track prefix + number (W3, SR5), never a bare ordinal ("phase 2"). Declare a new prefix once (grep for collisions), lead the section heading with it (### SR5 — …), and reference it verbatim everywhere — no invented monikers.
Headings are an outline: 3–5 genuine peer concepts as ##s, no catch-all buckets ("Details", "Misc"), no re-leveling to fake the count.
A plan's shape is free-form — let content pick the structure; prefer tables/diagrams over prose runs. Default to one PR: split into phases only for a real sequencing constraint, not to look thorough.
Architecture ⇄ implementation is a loop: a structural verdict (package-vs-module, electricity-vs-leaf) is contingent on an implementation choice — surface that choice as an explicit decision and state the verdict conditioned on it, in both directions. (Adopting an external engine reuses its electricity, leaving a thin leaf wrapper — don't miscount a dependency as a receptacle you own.)
A plan-of-record is build-ready or it is not done — written for the implementing agent: another agent can execute it straight through without asking anything. Before presenting, fix (don't leave for the user to catch):
- Open decisions: every fork that changes the build is resolved — bake low-stakes ones in as defaults; put the genuinely user-facing forks in one batched AskUserQuestion up front (mockup-rich previews).
- Template phrasing / vague hand-waving: every risk is named concretely with its mitigation; if a sentence would make an implementer ask "like what, specifically?", it isn't done.
- Unpinned proof-paths: a phase that exists to graduate or de-risk a specific code path names that path and carries a done-criterion only that path can satisfy — otherwise the implementer ships a green PR by the easiest route and the graduation silently doesn't happen.
- Phases a human can't verify: each phase states its user-visible delta ("none" when internal), a reproducible manual acceptance path (a test command is supporting evidence, not the path), and the sequencing reason it's separate.
Structural notes lead with an architecture diagram. Prefer a hand-authored inline SVG (<Svg svg={…} caption="…" />, file in src/diagrams/, imported ?raw; re-author wholesale, don't coordinate-patch) — colour as meaning, deliberate emphasis. A dense diagram must pass wide or its text renders unreadably tiny in the 46rem column. Reach for D2 (<D2 code={…} />) only when auto-layout of a large nested graph genuinely beats hand placement — then direction: down (right renders wide and shrinks text). Toss-up → SVG.
A note-local component is defined inline in the .mdx; promote to src/components/ only on reuse. Never hand-edit dist/.

atlas

Opções de instalação

Revise os arquivos de origem

Atlas note

1. Author

Atlas note

1. Author

2. Build & verify

3. Preview & share

4. Lifecycle

name	atlas
description	Create, update, or finalize a note in the kolu Atlas (docs/atlas) — frontmatter, the MDX component kit, build + check-sync, and the preview/share links. Use whenever authoring or editing an Atlas note (e.g. a /be plan-of-record).
argument-hint	<slug \| what the note is about>

atlas

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Atlas note

1. Author

Atlas note

1. Author

2. Build & verify

3. Preview & share

4. Lifecycle