All authors
Claude Skills by ArcticFox2029
github.com/ArcticFox202911 skills0 installs6 views
- BootstrapSet up chamnan in this repository for the first time — build the architecture index, measure how well the code describes itself, fill in missing file comments, and record a baseline. Run once per repo.Votes: 0GitHub stars: 9
- CaptureWrite down a procedure worth keeping — a multi-step process, a trap that cost real time, or something that has now come up three times. Use it the moment you finish such a task, while the details are still exact.Votes: 0GitHub stars: 9
- MilestoneRecord a change that reshaped the repository — what moved, why it was worth doing, and which areas it touched. Use after a migration, a rewrite, or a decision that changed how part of the system works.Votes: 0GitHub stars: 9
- PromoteTurn a scratch script into a permanent tool this repo keeps. Use when a check, report, or analysis has proved worth running more than once.Votes: 0GitHub stars: 9
- RemapRebuild the architecture index after files were added, removed, renamed, or restructured. Cheap to run; run it whenever the shape of the repo changed rather than waiting to be asked.Votes: 0GitHub stars: 9
- RememberRecord why something is the way it is — a decision and its reasoning, a lesson that cost time, or a standing constraint. Use when the reasoning behind a choice would be expensive to reconstruct later.Votes: 0GitHub stars: 9
- ReportShow what this workspace has actually done to context cost in this repo — weekly context-per-turn, before and after. Use when the user asks whether chamnan is worth keeping.Votes: 0GitHub stars: 9
- ResumeWrite down where this stretch of work stopped, so the next session continues instead of restarting. Use at the end of a working session, or when handing the repository to someone else.Votes: 0GitHub stars: 9
- DecideA reusable decision procedure, and a copyable prototype for the guard that encodes it — derive the population, set one threshold by what being wrong costs, name the offender, and break it once to prove it can fail. Use when writing a check, guard, gate or validation of any kind, or when deciding whether something is safe, done, duplicated, stale, or worth doing — so the shape is the same every time instead of re-derived per session.Votes: 0GitHub stars: 9
- ReviewReview a change with what this repository knows about it — who depends on the file, which tests cover it, what broke here before, and what the repo has written down. Use before approving a diff, opening a PR, or when asked to review.Votes: 0GitHub stars: 9
- WhyWork out whether a failure is your machine or your code before debugging either, using the environment this repository has declared and the dependency map. Use when a test, build or command fails and the cause is not obvious from the error.Votes: 0GitHub stars: 9