Skip to content

joetawil7/first-pass / skills/setup-first-pass

setup-first-pass

Unverified

Set up first-pass for a main folder that holds many repos, or for one repo. In a main folder it writes one set of working rules at the root that every session loads, a workspace map, and a section in each repo with that repo's real commands, test limits and invariants, and it lists each repo's own hooks so first-pass can run them from the main folder. In one repo it writes the rules and the section into that repo. Use when asked to set up, install, add, update or re-run first-pass, to "add the shipping rules", or when the start-of-session check says something drifted. Re-run to update.

FileKindSize
SKILL.mdskill md33.0 KB
assets/INVARIANTS.mdmarkdown801 B
assets/breaker.mdmarkdown9.5 KB
assets/machine-block.mdmarkdown1.3 KB
assets/profile-block.mdmarkdown5.7 KB
assets/project-block.mdmarkdown1.2 KB
assets/rules-block.mdmarkdown22.6 KB
assets/words-block.mdmarkdown1.6 KB
assets/workspace-block.mdmarkdown626 B

assets/machine-block.md

View on GitHub
<!-- first-pass:machine:start v0.9.3 (written by the setup-first-pass skill from this machine's survey; it describes this machine only and never goes in a file teammates share; re-run setup to refresh it, and put your own notes outside the markers) -->

## This machine (first-pass)

- **Machine:** {{machine}}
- **Heavy runs** (databases, browsers, emulators, media tools, full builds): {{heavy_runs}}
  This answer applies in every project on this machine, and it never covers a local run that
  reaches real people (email, SMS, push, payments, publishing to real accounts): that run asks
  first, unless it runs with the keys and switches its repo's section lists set, setting them
  stops it, and the section does not say it needs a yes; and a repo whose "Local runs that
  reach real people" line says "unknown", that has no such line, or that has no first-pass
  section asks before a server, a worker or an end-to-end or integration run.
- **Limits and cleanup:** {{limits}}
- **Looking at a UI running:** {{ui_tools}}
- Each repo's section says what its heavy runs and UI checks are; this block says how this
  machine runs them. A line in a repo's section written on another machine (a `.ps1` runner,
  a `C:\` or `$LOCALAPPDATA` path, `taskkill`) is read through this block.

<!-- first-pass:machine:end -->
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall