All authors
Claude Skills by p2p2sp
github.com/p2p2sp61 skills0 installs51 views
- ExtensionCreates or adapts an agent in the project's .claude/agents/ that a viber build runs at its close, just before the run is archived, with one forked skill in .claude/skills/ per phase when its work runs in phases one after another, and registers it as an entry of build.extensions in .claude/viber.yml. Use when the project needs a closing step of the project's own, for example end-user help files written after every task is committed.Votes: 0GitHub stars: 6
- FixerTraces a reported bug to its root cause and proves it with a failing test, then hands the diagnosis to the planner - it applies no fix itself. Use whenever user reports a bug and wants to fix it. Not for a fix the user asked to apply directly, without a plan.Votes: 0GitHub stars: 6
- HelpOpens the viber usage guide in the default browser.Votes: 0GitHub stars: 6
- ImplementorBuilds an approved plan task by task. Requires an existing plan; without one, suggest the viber:intent interview.Votes: 0GitHub stars: 6
- IntentPlanning interview - asks what the conversation and the code leave open, one question at a time, sizes the scope, proposes the spec shape and hands a confirmed summary to viber:planner. Never started unprompted. When a change looks like it needs a plan and no confirmed interview or viber:fixer diagnosis is in context, keep talking with the user and suggest, in one line, this interview or `plain plan mode` (Claude Code's own plan mode, no interview) for a small, well-understood change; invoke ...Votes: 0GitHub stars: 6
- MemoryReviews and repairs the host project's CLAUDE.md cascade - maps every node with its own size and the size of the chain a reader loads with it, creates the nodes a project with none needs, verifies each existing node against the code of the area it describes, brings every node below the root within budget, and resets the layer on demand. Use whenever the user wants to create, bootstrap, initialize, refresh, audit or reset project memory, or asks which nodes went stale, lost their area or grew ...Votes: 0GitHub stars: 6
- PlannerOnly for a confirmed viber:intent interview or a viber:fixer diagnosis already in context - never the entry point. Without one, suggest the viber:intent interview and let the user decide. Turns that input into a reviewed implementation plan - acceptance criteria, file map, then tasks carrying dependencies, contracts, verification and DoD.Votes: 0GitHub stars: 6
- PrototypeTurns a UI change into one working, self-contained HTML mockup in the project's own look - a single proposal or three variants to choose from - refines it in a UI-only conversation, then carries the conclusions to viber:intent, onto the GitHub issue it started from, or both. Takes the change in prose, or an issue number or URL when github.issues is on.Votes: 0GitHub stars: 6
- RulesReviews and repairs the host project's .claude/rules/ directory - maps every rule with its own size, the scope it declares and the number of tracked files that scope really matches, proposes the rules a scope with none needs, verifies each existing rule against the code it gates, and resets the layer on demand. Use whenever the user wants to create, review, audit, refresh or reset the project's coding rules, or asks which rules went stale, match nothing or grew past their budget.Votes: 0GitHub stars: 6
- TddRed-Green-Refactor cycle for a plan task marked `TDD: required`. Invoked only by `viber:task-coder`, never directly.Votes: 0GitHub stars: 6
- TriageReviews one reported issue against the current code - whether it can be done, how, what it affects and how big the change is - classifies it and names the next viber step without taking it. Takes a GitHub issue number or URL, or pasted issue text, and can post the report as a comment on the issue.Votes: 0GitHub stars: 6