Files
阿白叔andClaude Opus 4.7 ea1819f1d2 feat: rename to praxis, package as Claude Code plugin
Reframe team-guide as praxis (Greek for "practice"): Simgreek's coding
agent rulebook, distributed as a Claude Code plugin so SessionStart
hook can force-inject the using-praxis bootstrap.

- Add .claude-plugin/{marketplace,plugin}.json: makes this repo a
  one-plugin marketplace installable via /plugin marketplace add.
- Add hooks/{hooks.json,session-start,run-hook.cmd}: SessionStart
  hook reads using-praxis SKILL.md and injects it into context as
  hookSpecificOutput.additionalContext (Claude Code) or
  additional_context (Cursor) or additionalContext (Copilot CLI).
- Migrate library/<topic>/SPEC.md → skills/<topic>/SKILL.md with
  YAML frontmatter (name + when-to-invoke description).
- Add skills/using-praxis: bootstrap with iron law, red-flags table,
  catalog, instruction priority, sub-agent stop, Codex/Cursor fallback.
- Add skills/debugging: 4-phase root-cause investigation with
  3-fixes-failed → architectural problem rule.
- Add skills/verification: evidence-before-claims gate with
  rationalization table.
- Drop library/, references in AGENTS.md updated to skills/.
- Rename throughout: team-guide → praxis.
- README rewritten with both install paths (plugin / external spec)
  and updated bootstrap prompt.

Codex / Cursor / non-Claude users still get the spec by reading
AGENTS.md and skills/ files manually — only the auto-injection
requires Claude Code.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-25 18:02:48 +08:00

5.7 KiB

name, description
name description
using-praxis Use when starting any conversation in a Simgreek project — establishes how to find and use praxis skills, requiring Skill tool invocation before ANY response including clarifying questions
If you were dispatched as a subagent to execute a specific task, skip this skill — your dispatcher already loaded praxis context. If you think there is even a 1% chance a praxis skill might apply to what you are doing, you ABSOLUTELY MUST invoke it.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this.

Using Praxis

Praxis is the Simgreek team's coding agent rulebook — Greek for "practice." It exists because human teammates have been bitten by every shortcut you are about to take. The skills below encode those scars.

Instruction Priority

Praxis skills override default agent behavior, but the user's explicit instructions always take precedence:

  1. User's explicit instructions (project AGENTS.md, CLAUDE.md, direct chat) — highest
  2. Praxis skills — override default behavior where they conflict
  3. Default agent behavior — lowest

If a project's AGENTS.md says "skip the encoding check this once" and a skill says "always check encoding," follow the user. They own the project. You are a guest.

How to Access Skills

In Claude Code: Use the Skill tool. When you invoke a skill, its full content is loaded — follow it directly. Never use Read on a skill file when Skill is available.

In Codex / Cursor / others: Skills live as markdown files under <plugin-root>/skills/. Read the relevant ones with the file-reading tool.

The Rule

Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means you must check. If an invoked skill turns out to be wrong for the situation, drop it — but you have to check first.

This includes:

  • Before answering a clarifying question
  • Before exploring the codebase
  • Before "just running git status"
  • Before reading docs to understand the project
  • Before announcing what you're going to do

The skill check is the first thing that happens after you receive a message in a praxis-enabled project. Not the second. Not "after I look around real quick." First.

Red Flags — These Thoughts Mean STOP

If you catch yourself thinking any of these, you are rationalizing past a skill. Stop, invoke the skill, then proceed.

Thought Reality
"This is just a simple question" Questions are tasks. Check for skills.
"I need more context first" Skill check comes BEFORE clarifying questions.
"Let me explore the codebase first" Skills tell you HOW to explore. Check first.
"I can just check git status / read a file quickly" Files lack conversation context. Check for skills.
"Let me gather information first" Skills tell you HOW to gather information.
"This doesn't need a formal skill" If a skill exists, use it.
"I remember this skill" Skills evolve. Read the current version.
"This is a small change" Small changes ship the bugs. Use the skill.
"The skill is overkill" Simple things become complex when skipped.
"I'll just do this one thing first" "One thing first" is how skills get bypassed.
"This feels productive" Undisciplined motion wastes time. Skills prevent it.
"The user is in a hurry" Skipping skills makes everything slower, not faster.
"I know what that means" Knowing the concept ≠ following the procedure. Invoke.

The Praxis Skill Catalog

Read the catalog before your first action in this project. Match each candidate skill against the current task.

Skill When it applies
git-upload Pushing to a remote, first push, adding new file types, leaked secret
nodejs-project Any project with package.json — task execution SOP including encoding checks
debugging Any bug, test failure, unexpected behavior, before proposing a fix
verification About to claim work is complete, fixed, or passing

If multiple apply, use them in order: process skills (debugging) before implementation skills (nodejs-project); verification (verification) before declaring done.

Skill Priority

When multiple skills could apply:

  1. Process skills first (debugging) — they determine HOW to approach the task
  2. Implementation skills second (nodejs-project, git-upload) — they guide execution
  3. Verification last (verification) — before declaring done

"Fix this bug" → debugging first, then nodejs-project if Node-relevant. "Push my changes" → git-upload first, then verification before declaring done.

Skill Types

Rigid skills (debugging, verification): follow exactly. The discipline is the value. Don't adapt away the steps you find inconvenient.

Flexible skills (nodejs-project SOP, git-upload pitfall list): adapt principles to context. The SOP is a default; deviate when the context demands and state the deviation explicitly.

The skill itself tells you which type it is.

User Instructions

User instructions describe what to do, not how. "Add this feature" or "fix this bug" does not mean skip the workflow. The user sets the destination; praxis sets the route.

What to Do Now

Before your next action:

  1. Identify which skills in the catalog above might apply (1% threshold).
  2. Invoke each one via the Skill tool (or read the file).
  3. Follow its checklist.
  4. Then proceed.

If the task is something praxis genuinely doesn't cover (e.g., "summarize this article"), proceed without a skill — but the check itself is mandatory.