All authors
Claude Skills by erickb336
github.com/erickb33635 skills0 installs0 views
- Remote ControlSet up Remote Control, so that the user can follow, steer and start Claude Code sessions from the Claude app on a phone. It turns Remote Control on for every new session, and it can run a server in a folder (such as ~/workspace) that starts at each login. Use when the user asks to reach sessions or start new ones from a phone, or to set up, check or undo Remote Control. Claude Code only.Votes: 0GitHub stars: 2
- ReportThe report that every sage agent ends with: STATUS, RESULT, EVIDENCE, FINDINGS, QUESTIONS, NOT VERIFIED, BRANCH. Use at the end of any task that the sage chief of staff gave you. Claude Code only.Votes: 0GitHub stars: 2
- Sage HelpHelp with sage: how to set it up, switch sage mode and autopilot, read the board, answer the chief's questions, pick a skill or a principle, fix a run that went wrong, and find where sage keeps its files. The user types /sage:sage-help (or /sage-help) with a question. Load it only when the user types it; do not load it on your own. Claude Code only.Votes: 0GitHub stars: 2
- SageThe state tool of sage mode: records tasks, routes, agent runs, findings, verdicts by head SHA and the user's gates in ~/.claude/sage/<project>/. Use in sage mode for every change of a task's state, and before any merge. Claude Code only.Votes: 0GitHub stars: 2
- SageUse Sage's task logbook, board and skill-led team workflow in Codex. Apply to Sage mode phrases, task coordination, findings and progress requests. Loading this skill does not activate Sage mode.Votes: 0GitHub stars: 2
- DictionaryThe sage dictionary: sage's approved words, one meaning each, and the words not to say. Apply to any text an agent writes for a person in sage mode: briefs, reports, findings, pages and the README.Votes: 0GitHub stars: 2
- Principle Attack The PremiseAttack the premise. Apply when two or more fixes that share one premise have failed the same check or review.Votes: 0GitHub stars: 2
- Principle Boundary DisciplineBoundary discipline. Apply when reviewing or writing validation, error handling or framework adapters.Votes: 0GitHub stars: 2
- Principle Build The LeverBuild the lever. Apply when the work is not trivial: edits, migrations, analyses or checks.Votes: 0GitHub stars: 2
- Principle Contextualize And Write For The ReaderContextualize and write for the reader. Apply when writing anything someone else will read later: a design, a handoff, findings, a report, a verification, a brief, a reply.Votes: 0GitHub stars: 2
- Principle Encode Lessons In StructureEncode lessons in structure. Apply when writing the same instruction a second time, or noticing a correction that keeps recurring.Votes: 0GitHub stars: 2
- Principle Exhaust The Design SpaceExhaust the design space. Apply when a new interaction or an architectural choice has no precedent in the code.Votes: 0GitHub stars: 2
- Principle Experience FirstExperience first. Apply when a product, UX or scope trade-off comes up.Votes: 0GitHub stars: 2
- Principle Explain The NumberExplain the number. Apply when you plan a measurement, or you trust, report or act on a number that you measured: a speedup, a regression, a throughput, a latency or an eval result.Votes: 0GitHub stars: 2
- Principle Fix Root CausesFix root causes. Apply when debugging a failure or repairing a finding.Votes: 0GitHub stars: 2
- Principle Foundational ThinkingFoundational thinking. Apply when before writing logic, when choosing core types and data structures or ordering scaffold against features.Votes: 0GitHub stars: 2
- Principle Guard The Context WindowGuard the context window. Apply when the context fills up: large outputs, long files, repeated reads or planning a fan-out.Votes: 0GitHub stars: 2
- Principle Laziness ProtocolLaziness protocol. Apply when refactoring, judging a diff's size, or tempted to add an abstraction, a layer or a threaded signal.Votes: 0GitHub stars: 2
- Principle Make Operations IdempotentMake operations idempotent. Apply when you design commands, lifecycle steps or processing loops that run among crashes, restarts and retries.Votes: 0GitHub stars: 2
- Principle Migrate Callers Then Delete Legacy ApisMigrate callers, then delete legacy APIs. Apply when a change introduces a new internal API while callers of the old one still exist.Votes: 0GitHub stars: 2
- Principle Minimize Reader LoadMinimise reader load. Apply when reviewing or shaping code that is hard to follow.Votes: 0GitHub stars: 2
- Principle Model The DomainModel the domain. Apply when you write stateful logic, or code branches a lot or repeats an assumption about a shape across files.Votes: 0GitHub stars: 2
- Principle Never Block On The HumanNever block on the human. Apply when tempted to ask \"should I do X?\" about reversible work.Votes: 0GitHub stars: 2
- Principle Outcome Oriented ExecutionOutcome-oriented execution. Apply when a planned rewrite or migration has explicit phase boundaries.Votes: 0GitHub stars: 2
- Principle Prove It WorksProve it works. Apply when before declaring a task done, or when judging a claim that something works.Votes: 0GitHub stars: 2
- Principle Redesign From First PrinciplesRedesign from first principles. Apply when you add a new requirement to an existing design.Votes: 0GitHub stars: 2
- Principle Separate Before Serializing Shared StateSeparate before serializing shared state. Apply when concurrent actors might write to the same file, branch, key or state object.Votes: 0GitHub stars: 2
- Principle Sequence Verifiable UnitsSequence verifiable units. Apply when multi-step work (a sweep, a migration, a run of similar edits) or the order of commits in a change.Votes: 0GitHub stars: 2
- Principle Subtract Before You AddSubtract before you add. Apply when ordering an addition, a refactor or a rewrite.Votes: 0GitHub stars: 2
- Principle Test Behavior Not ImplementationTest behaviour, not implementation. Apply when writing, changing or keeping a test.Votes: 0GitHub stars: 2
- Principle Type System DisciplineType system discipline. Apply when you design types, review a function signature or write code in a statically typed language.Votes: 0GitHub stars: 2
- Readme GuideWrite a project README. Apply when you write, change or review a README of any project, in any language.Votes: 0GitHub stars: 2
- Writing StandardWrite at 80% of Simplified Technical English. Apply to any text an agent writes for a person: messages, reports, specs, findings, reviews, plans.Votes: 0GitHub stars: 2
- ReportThe report that every sage agent ends with: STATUS, RESULT, EVIDENCE, FINDINGS, QUESTIONS, NOT VERIFIED, BRANCH. Use at the end of any task that the sage chief of staff gave you. Claude Code only.Votes: 0GitHub stars: 2
- PresentationPresent to the owner: each kind of message, its parts in order, the pictures, the pages and the message command. Apply to every message that the chief sends to the owner in sage mode: a progress note, a question, a report, a catch-up, a design, and the other kinds below.Votes: 0GitHub stars: 2