All authors
Claude Skills by receptron
github.com/receptron137 skills0 installs47 views
- ScaffoldCreate the app skeleton: web app, Cloud Functions workspace, emulator config and the rules test harness.Votes: 0GitHub stars: 234
- SpecWrite .blueprint/spec.md from the interview answers and the base and usecase spec templates, and list what is still undecided.Votes: 0GitHub stars: 234
- Audit LogRecord every privileged action in a collection only functions can write and only admins can read.Votes: 0GitHub stars: 234
- Domain RestrictionLimit sign-in to the company's email domain, twice: in blocking functions and in the rules.Votes: 0GitHub stars: 234
- OffboardingLock a leaver out at once: revoke refresh tokens, drop claims, disable the user, and make the rules refuse old tokens.Votes: 0GitHub stars: 234
- Production AuthPut the sign-in restriction live on production before the site is: deploy functions and rules only, then register the blocking functions.Votes: 0GitHub stars: 234
- RolesRoles in custom claims, granted only by an admin-only callable function; the first admin by a one-off script.Votes: 0GitHub stars: 234
- Verify DevConfirm the company-domain blocking functions are registered and running on the dev project.Votes: 0GitHub stars: 234
- ApiExpose the spec's operations as a validated JSON API under /api, with tests.Votes: 0GitHub stars: 234
- AuthAdd the sign-in the spec asks for; with none, keep the app reachable from this computer only.Votes: 0GitHub stars: 234
- DataTurn the spec's tables into SQLite migrations with node:sqlite, and prove them with tests.Votes: 0GitHub stars: 234
- HandoverWrite the README the user needs: how to start it, where the data is, and how to back it up.Votes: 0GitHub stars: 234
- PrerequisitesCheck Node (a version with node:sqlite) and yarn are available.Votes: 0GitHub stars: 234
- Run CheckBuild for production, start it, and make sure the screen and the API answer.Votes: 0GitHub stars: 234
- ScaffoldCreate the app skeleton: Express API, SQLite through node:sqlite, a Vue screen, and the test harness, following the layout the later checks rely on.Votes: 0GitHub stars: 234
- SpecWrite .blueprint/spec.md from the interview answers and the base and usecase spec templates, and list what is still undecided.Votes: 0GitHub stars: 234
- UiBuild the spec's screens in Vue and wire them to the API.Votes: 0GitHub stars: 234
- PolishPolish the next file on the list to the house style without changing what it says, keep the original, and check it.Votes: 0GitHub stars: 234
- ReportReport what was polished, what was checked, and what was left as it was.Votes: 0GitHub stars: 234
- SurveyMeasure the named documents with chaff and choose which to polish, within the agreed number — changing nothing yet.Votes: 0GitHub stars: 234
- Acceptance FirebaseProve each must-have from the spec works end to end against the emulators, as the users the spec names — and fails for everyone it should fail for.Votes: 0GitHub stars: 234
- AcceptanceProve each must-have from the spec works end to end, one test per must-have.Votes: 0GitHub stars: 234
- Features FirebaseBuild the spec's must-haves on Firebase: the screens and client logic, working inside the Firestore rules, proven against the emulators.Votes: 0GitHub stars: 234
- ReportWrite up what this campaign changed, how each change was proved, what was not proved, and what was declined and why.Votes: 0GitHub stars: 234
- SurveyFind what is worth tidying in this repository, measure each candidate's value and risk, and write a plan the person approves — including what to leave alone and why.Votes: 0GitHub stars: 234
- TrancheTake ONE target from the plan and land it without changing behaviour: guard it on the untouched code, move it verbatim, prove the equivalence by running both, mutation-sweep the tests, pass every gate, open a PR and merge it on green CI — or decline it with the cost written down.Votes: 0GitHub stars: 234
- BaselineFind the repository's own gates — install, format check, lint, typecheck, build, test — record them, and prove they all pass before anything is touched.Votes: 0GitHub stars: 234
- CiFind out whether GitHub Actions already runs the recorded gates on every pull request, and record what is missing. Change nothing: adding CI is the first change the person approves.Votes: 0GitHub stars: 234
- StateConfirm the folder is a clean clone of a GitHub repository on its up-to-date default branch, and keep the build's own notes out of git.Votes: 0GitHub stars: 234
- ProposePropose a fix for each finding and write a corrected copy of each document beside the original, leaving the original untouched.Votes: 0GitHub stars: 234
- ReportReport what was found, what was checked, and what could not be checked.Votes: 0GitHub stars: 234
- CounterProve the style bites: write texts that deliberately break the guide and confirm chaff reports them.Votes: 0GitHub stars: 234
- ReportReport what became a machine rule, what went to the guide, and what was left out and why.Votes: 0GitHub stars: 234
- RulesMeasure the models with chaff, then write the style twice: chaff.yaml for what a machine checks, STYLE.md for what the writer reads — with a reason for every decision.Votes: 0GitHub stars: 234
- SourcesCollect the texts the person wants as models into .blueprint/sources/ as Markdown, and record where each came from.Votes: 0GitHub stars: 234
- BriefTurn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.Votes: 0GitHub stars: 234
- DraftWrite the next part of the outline to the house style, check it with chaff, cite what came from the sources, and mark it done.Votes: 0GitHub stars: 234
- OutlineSplit the document into parts — each with its file, the points it must cover and a length — without touching any existing file.Votes: 0GitHub stars: 234
- HelloAdd a page that shows the greeting the user gave in the interview. A dummy step for trying the market.Votes: 0GitHub stars: 234
- SecurityBefore production, review the app against OWASP Top 10:2025, fix what is exploitable, prove it on the emulators, and redeploy dev.Votes: 0GitHub stars: 234
- SecurityReview the finished app against OWASP Top 10:2025, fix what is exploitable, prove each fix with a test, and report.Votes: 0GitHub stars: 234
- ExtractExtract every dated event, time and amount from the named documents into .blueprint/facts.json, each with a quotation it was read from — deciding nothing yet.Votes: 0GitHub stars: 234
- ReportReport every problem the machine found in the extracted facts, in plain words, with where it is and how to fix it.Votes: 0GitHub stars: 234
- ApiBuild the spec's operations as the Worker's API, with validation and tests.Votes: 0GitHub stars: 234
- AuthPut in the sign-in the spec chose; a published Worker is open to anyone.Votes: 0GitHub stars: 234
- DataTurn the spec's tables into D1 migrations with tests.Votes: 0GitHub stars: 234
- DeployWith approval, create the D1 database, apply the migrations, and publish with wrangler deploy.Votes: 0GitHub stars: 234
- HandoverWrite the README and the first page: where the app is, how to run and publish it, and how to back up its data.Votes: 0GitHub stars: 234
- PrerequisitesCheck Node and yarn; wrangler comes with the project, and signing in to Cloudflare waits for the publish step.Votes: 0GitHub stars: 234
- Run CheckBuild, run it with wrangler dev, and make sure the screen and the API answer.Votes: 0GitHub stars: 234