All authors
Claude Skills by skrrt-sh
github.com/skrrt-sh18 skills0 installs0 views
- Design PrinciplesRules for writing and changing code. DRY, loose coupling, separation of concerns, the simplest design, root-cause fixes, complete state machines, no destructive changes, and deleting the code a change replaces. Use when implementing a feature, fixing a bug, refactoring, replacing an approach, adding a module, or planning a large change.Votes: 0GitHub stars: 2
- Herdr AgentsDispatch subagent scopes as real coding agents in Herdr. One git worktree, one workspace, and one named agent per scope. Exchange mail with them, integrate their diffs, and delete the worktrees. Use when running inside Herdr (HERDR_ENV=1) and the user wants agents in worktrees, Herdr panes, or parallel work on separate checkouts, or wants to message or clean up those agents. Not for installing Herdr or operating a single pane. The subagents skill still owns planning, briefs, and review.Votes: 0GitHub stars: 2
- ReportingHow to report to the user, when to ask, and how to finish. Plain short words, defined terms, concrete specifics, done or not done per ask, open questions as one numbered list with recommendations at the end, no mid-run questions, no handing work back. Use whenever the user asks where things stand or what is next, asks for a status update, summary, or simpler explanation, asks for a reply or email drafted in their tone, asks for a diagram, or says to work start to finish without asking; and fo...Votes: 0GitHub stars: 2
- ResearchResearch before designing or deciding. Read current official docs, study how established projects and peers solve the same problem, cross-check sources, and verify claims against the code. Use before choosing an approach, library, architecture, or vendor, when asked how others do it or for best practices, and when a claim, fact, or API detail is uncertain.Votes: 0GitHub stars: 2
- Self DocumentingKeep comments and docs to the minimum so the code stays the single source of truth. Comments state why in three lines at most. Docs record decisions, never how the code works. AGENTS.md is the only instruction file and holds how to work, never the state of the code. Prose never points into the code. Every change fixes or deletes the prose it makes false. Use whenever writing or editing code, comments, docstrings, READMEs, design docs, AGENTS.md, CLAUDE.md, rules, or skills, even if the reques...Votes: 0GitHub stars: 2
- SubagentsOrchestrate subagents to implement code changes. The main thread plans, briefs, dispatches, and reviews. Strictly scoped subagents on Opus write the code. Use for any implementation, audit, or fix that is more than a one-line edit, whenever the user asks for subagents, parallel work, or handing work to agents, even without the word subagent.Votes: 0GitHub stars: 2
- TestingDecide which tests to write, keep, and delete, and prove a change works before calling it done. Test only business logic and its corner cases. Run the real thing on every target before reporting a fix. Delete tests for removed or replaced behavior. Use when writing, adding, reviewing, or cleaning up tests or specs, when fixing a bug or a flaky test, before reporting any change as done, or when a change removes or replaces behavior that tests cover.Votes: 0GitHub stars: 2
- Md WriterWrite or edit knowledge-base Markdown with frontmatter, Mermaid diagrams, related-document links, and markdownlint validation. Use for guides, specs, ADRs, runbooks, and API documentation; not repository meta files such as README, CHANGELOG, CLAUDE.md, AGENTS.md, or SKILL.md.Votes: 0GitHub stars: 2
- CommitCreate focused conventional commits with a mandatory gitmoji. Use when the user asks to commit, write a commit message, or split changes into commits.Votes: 0GitHub stars: 2
- PrPush a branch, open or update its GitHub pull request or GitLab merge request, and merge it when asked. Use when the user asks to open, update, or merge a PR or merge request.Votes: 0GitHub stars: 2
- ReleaseDraft, prepare, tag, or publish a GitHub or GitLab release. Use whenever the user asks for release notes or a release description, a summary of what changed for a version or since the last tag, or to prepare, tag, or publish a release. Not for deleting or moving existing tags.Votes: 0GitHub stars: 2
- SetupConfigure this repository for the Skrrt ship workflows and select a branching strategy. Run once before commit, pr, and release.Votes: 0GitHub stars: 2
- StatuslineInstall the skrrt Claude Code status line, a Catppuccin Mocha pill bar showing model, folder, git branch, lines changed, context use, and the 5-hour and weekly rate limits. Use when the user asks to install, set up, update, or restore the skrrt status line.Votes: 0GitHub stars: 2
- Design SystemKeep every screen inside one visual system so a fix in one place fixes it everywhere. Tokens, one component per pattern with full states, stable sizes, one icon set, close controls on every overlay, and fixes in the system. Use for any UI change on web, mobile, or desktop: building or editing components, screens, themes, tokens, icons, toasts, modals, or sheets, and when matching a design file. Looks and wording belong to taste, motion to motion.Votes: 0GitHub stars: 2
- MotionThe project's motion settings on top of Emil Kowalski's and Apple's motion skills, loaded when installed. Use when adding, changing, reviewing, or auditing any animation, transition, hover, gesture, swipe, spring, or haptic, or when something snaps, jumps, or feels janky, on web or Expo/React Native.Votes: 0GitHub stars: 2
- ScreensShip each screen complete, predictable, fast, and matched to the design. Every real state handled, one established pattern per action, big flows split into steps, only visible rows rendered, and checks in the real UI on every target. Use when building, changing, or reviewing any screen, page, view, flow, or form on web, mobile, or desktop, and when the UI shows a wrong or stale state, double-fires on repeated taps, lags, or misses a loading, empty, or error state. Design process belongs to ux...Votes: 0GitHub stars: 2
- TasteHow a page or screen looks and reads. Use when laying out or reviewing a page, hero, or sections, fixing layout, spacing, typography, fonts, or contrast, when UI looks bad, ugly, sloppy, or like AI slop, or when writing copy, headlines, CTAs, button labels, error and empty-state text, or tone, or text is salesy, cringy, or repetitive. Design process belongs to ux-patterns, states to screens, tokens and components to design-system, motion to motion.Votes: 0GitHub stars: 2
- Ux PatternsDesign process to run before any UI is drawn or built. Complete user stories for the least-expert and power user, then established patterns from peers and platform guidelines, then product-specific principles, then a design where every element traces to a story, delivered as a short brief in chat. Use when asked to design or redesign anything, for a new feature, screen, flow, page, or landing page, or when asked how something should work or what users expect.Votes: 0GitHub stars: 2