All authors

Claude Skills by soumyaRauth
github.com/soumyaRauth18 skills0 installs5 views
- ISSUE TEMPLATE<!-- kebab-case, e.g. change-guard -->Votes: 0GitHub stars: 10
- Api Contract GuardUse when adding or changing an interface that consumers deploy separately from: an HTTP or GraphQL API endpoint, a webhook, an event or queue message, a public SDK or library API, or CLI output other tools parse, for mobile apps, partners, other services or public API users. Matches the project's existing conventions, settles the decisions that cannot be taken back once someone integrates, and classifies a change as additive, behavioral or breaking, with a migration path. Not for internal fun...Votes: 0GitHub stars: 10
- Architecture EngineerUse when asked to design a system or a new application's structure, review or rework an architecture, choose between architectural options such as monolith or services, decide where a responsibility belongs, or plan an architectural migration. Separates what is required from what is assumed, reads how an existing system is really built, compares genuine options, records each decision with what would reverse it, and stages the migration. Not for ordinary features, bug fixes, refactors inside o...Votes: 0GitHub stars: 10
- Dependency GuardUse when a request would install, add, replace or switch a dependency (package, SDK, framework, build tool, GitHub Action, container base image), upgrade one to a new major version, or asks which library to use or whether to add one. Checks whether the need is already met, whether the package is the one intended (no typosquat or invented name), what it brings in, and whether it is maintained, and answers USE EXISTING, ADD, ADD WITH CONDITIONS or DON'T ADD. Not for routine patch or minor bumps...Votes: 0GitHub stars: 10
- Deployment CompatibilityUse when a deployment target is named or declared in the repository (a server spec, fly.toml, render, railway or vercel config, a compose or Kubernetes file for a named host), when asked whether the app can be deployed or run on a server, a VPS, a cloud or Docker host, staging or production, or when something works locally and fails on the server. Compares what the project requires with what the target provides, answers READY, READY WITH CONDITIONS, BLOCKED or NOT ASSESSED with evidence, fixe...Votes: 0GitHub stars: 10
- Engineering InvestigatorUse when someone asks why something is happening, reports a vague, intermittent or unexplained problem (slowness, random failures, wrong or missing data, a production incident, works locally but fails on the server, a regression after a deploy, a fix that did not hold), or asks to resume an investigation. Forms competing hypotheses, runs the smallest discriminating experiment, and says whether the application, a dependency, the infrastructure or the client's network is responsible, with a con...Votes: 0GitHub stars: 10
- Impact MapUse before changing anything other code depends on: renaming, splitting, merging or removing a status, enum, field, table, column, route or shared concept, or changing a schema, API response, event, configuration or cross-module behavior; and when asked for the blast radius, or what a change or PR missed. Traces callers, jobs, reports, raw SQL, string comparisons, fixtures, permissions and tests, including couplings no import shows, and returns the surface with evidence and confidence. Read-o...Votes: 0GitHub stars: 10
- Practical LocalizerUse when adding a locale or language, translating or reviewing locale files, fixing plural, date, number or currency formatting, right-to-left layout, or asking whether translated copy sounds natural. Writes natural, context-aware product copy rather than literal translation, and keeps placeholders, ICU plurals, locale formatting and terminology intact. Modes: analyze, localize (locale resources only), review. Not for English-only copy changes in an app with no translation catalogs.Votes: 0GitHub stars: 10
- Production GuardUse when someone asks whether a change, branch, release or the application is safe or ready to ship, merge, release, deploy or go to production, and when meaningful work on money, authentication, authorization, migrations, bulk or destructive operations, multi-tenancy or external integrations is being wrapped up. Checks behavior, regressions, failure modes, idempotency, security and tenancy, data integrity, performance at volume and recovery, runs the project's own checks where possible, and ...Votes: 0GitHub stars: 10
- Project CompassUse when asked what to build next, whether to add something, or what is being missed; when a request adds another instance of a recurring pattern (another status, permission exception, option or workaround); when it locks in a data model or public contract; or when the repository keeps .project-compass/. Works out what the project is becoming, notices systems nobody defined and undecided business rules, and turns that into one next step. Mostly silent: build it is the default. Not for renames...Votes: 0GitHub stars: 10
- Proof Driven DevUse for any request to add, build, implement or fix behavior whose success is not obvious from the diff: a new app, tool or CLI built from a spec, features, bug fixes, refactors that must preserve behavior, migrations, performance or security changes. Turns the request into numbered observable requirements, including unstated negative cases and boundaries, implements, runs the checks that prove each one, and reports VERIFIED, REVIEW REQUIRED or BLOCKED instead of narrating edits. Not for copy...Votes: 0GitHub stars: 10
- Skills PipelineUse when the user types /skills-pipeline or explicitly asks for the skills pipeline by name, and only then. Runs the Skills Hub skills the user picks from a numbered menu, in the order picked, and ends in a ledger of every stage. Not for any request that does not name it, however large or risky; naming one skill ("use Impact Map") engages that skill, not this.Votes: 0GitHub stars: 10
- Standards CompassUse when implementing or changing sign-in, sign-up, password reset, sessions, roles, permissions or admin actions, payments or refunds, personal or sensitive data (including exports and new fields that hold it), file uploads, AI or LLM features, or accessibility-relevant UI; when a change weakens an existing control; and when asked which standards apply, for a security review, or for an audit. Names what the feature must account for, builds it in and checks it; audits report evidence-backed g...Votes: 0GitHub stars: 10
- Delivery LeadUse when the user asks to work through the backlog, plan or tickets on their own: \"take the next ticket\", \"keep going until the milestone is done\", \"build the whole thing\", or names delivery-lead. Picks the next ready ticket from .delivery/, drives it to done on a branch with the disciplines engaged and ProofBuild VERIFIED, then the next, until the milestone ships, the run budget is spent, or a human is needed; ends in a run ledger. Not for a single ordinary request however large, a req...Votes: 0GitHub stars: 10
- Delivery PlannerUse when asked to plan the work, break a spec or large feature into milestones and tickets, set up or connect a tracker (Jira, Trello, Nextcloud Deck, GitHub, GitLab, Linear, or local files), create, update, move or close tickets, or asked what is left; and passively when work starts or finishes in a repository that keeps .delivery/. Writes vertical-slice tickets with numbered acceptance criteria and keeps the tracker in sync without duplicates or lost human edits. Not for a single small task...Votes: 0GitHub stars: 10
- Observability BaselineUse when an app is about to get its first production deploy with no monitoring, when asked to set up logging, monitoring, alerting, error tracking, uptime checks, health endpoints, backups or a runbook, when asked how we will know if production breaks, and when a postmortem shows nobody noticed. Puts a one-developer baseline in place (structured logs, health endpoints, error tracking, an external uptime check, one alert a human reads, a restore-tested backup, docs/runbook.md) and proves each ...Votes: 0GitHub stars: 10
- Project KickoffUse when someone wants to start a new app, project or product from an idea, or when the repository is empty or holds only a README or notes and the request is to build something whole: \"I want to build an app where...\", \"start a new project for...\", \"where do I start?\", or a detailed spec pasted in to build from scratch. Asks only the product questions that change what gets built, writes docs/spec.md with every claim labelled, picks a boring stack the developer already knows, scaffolds ...Votes: 0GitHub stars: 10
- Release EngineerUse when asked to set up or fix CI/CD, a pipeline (GitHub Actions, GitLab CI or another), automated deploys, staging or production environments, secrets in CI, a release or versioning, rollback, or a zero-downtime or migration-safe deploy, or to deploy or ship now when no repeatable path exists. Builds PR checks, a build-once artifact, staging on merge, gated production promotion, smoke checks and a tested rollback, and reports only what actually ran. Not for comments or formatting in CI file...Votes: 0GitHub stars: 10