using-praxis
Use at session start to learn how Praxis skills are invoked and why triage runs before every task.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- using-praxis
- description
- Use at session start to learn how Praxis skills are invoked and why triage runs before every task.
03 SKILL.md 正文
Using Praxis
You have Praxis.
<EXTREMELY_IMPORTANT> Before any response or action on every user message, classify scope using the triage table below, announce it, then load required skills in parallel. </EXTREMELY_IMPORTANT>
Triage
One line before every response:
praxis: scope=<x>, loading=<skills> # single-module (default)
praxis: scope=<x>, topology=multi-module, loading=<skills> # multi-module
| scope | signal | load |
|---|---|---|
| vague | problem space undefined — can't yet say what to build, for whom, or whether it's worth building | design |
| trivial | typo, rename, docs-only, <=1-line, pure Q | none |
| small | one function, single file, <=50 LOC, or test-only change | tdd (intent unclear? clarify first) |
| standard | feature or source-code change | design, plan, tdd, review |
| complex | new system, >=5 tasks, or parallel edits | design, plan, worktree, subagents, review, ship |
| debug | broken, regression, failing test | debug |
| onboard | existing project, no docs/tech-spec.md | onboard |
Topology is declared alongside scope, not chosen from the table. Default single (omit it). Announce topology=multi-module when one change spans multiple modules or repositories - every loaded workflow skill then follows skills/references/multi-module.md. Multiple repositories require a user-designated existing coordinator repository. Once a multi-module change is underway, a coordinator spec/plan declaring topology: multi-module exists on disk; read it and carry topology=multi-module forward every turn - do not re-decide from scratch. If unsure, check for that declaration before announcing.
topology doesn't change scope: classify exactly as for single-repo work; multi-module only adds execution mechanics (multi-module.md). Unsure? Start single-module; upgrade the declaration once confirmed.
If multiple scopes fit, choose the smaller one. vague is a last resort — if you can name a rough deliverable, use a lower scope instead. feature change = user-visible/public-contract change. source code = code/schema/config that changes shipped behavior; docs, tests, examples, CI, and tooling excluded.
Rule
- Unfamiliar with this project? Read
docs/tech-spec.mdfirst. - Classify inline using the table above — no skill-loader call needed for triage.
- Announce:
praxis: scope=<x>, loading=<skills>(addtopology=multi-modulewhen the change spans multiple modules - see Topology above) - Load all required skills in parallel (single response): use the harness skill loader when available (
praxis:<name>/ native skill tool), otherwise readskills/<name>/SKILL.mdwith the native file-read tool. - Follow loaded skills literally; respect
<gate>markers. - Search code shapes with structural search (no index needed, works in any repo); plain grep only when structure is irrelevant.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.