Skip to content

epistex-dev/poteto-kit / templates/skills/team-mode

team-mode

Unverified

Router for {{OWNER}}'s way of working. Use for "{{OWNER}} mode", "/team-mode", or when asked to work to this team's standard of rigor (concise detailed answers, deliberate subagents, plain prose, simple code, verified work). Routes each situation to the leaf skill or playbook that owns it.

principles/_principle.template.md

View on GitHub
<!-- HOW TO USE:
1. One principle per file, named <principle>.md (kebab-case verb phrase). A principle is a short rule of judgment that changes concrete decisions; it is cited in replies ("principle X changed Y"), so it must be specific enough that a citation can be checked.
2. Copy the template block below to principles/<principle>.md (next to this file, inside the team-mode skill folder), fill it, and link the file from ../SKILL.md as `principles/<principle>.md`. Four filled principles ship next to this file (`fix-root-causes.md`, `boundary-discipline.md`, `encode-lessons-in-skills.md`, `script-the-deterministic-parts.md`): keep, edit or delete them, and keep the links in ../SKILL.md in sync. Do not install this underscore file.
3. Source a principle from an observed failure or a review comment that keeps recurring (the failure loop in ../SKILL.md). If the rule can be a lint rule or a type, make it one and let the principle point at it.
4. Keep each under ~25 lines. Delete this comment block in the files you install.
-->

# Template

```markdown
# {{principle-name}}

**Rule:** {{one sentence, imperative.}}

**Why:** {{the failure it prevents and what that failure costs.}}

**In practice:**
- {{a concrete behavior or decision it changes}}
- {{another}}

**Tells you are violating it:** {{observable signs in a diff, a plan or a reply.}}

**Enforced by:** {{a lint rule, CI check or type if one exists; otherwise "soft: this file only".}}
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall