All authors
Claude Skills by receptron
github.com/receptron137 skills0 installs47 views
- ScaffoldLay out a Worker with D1 and static Vue assets, with tests that run inside the Workers runtime.Votes: 0GitHub stars: 234
- SecurityReview the finished Worker against OWASP Top 10:2025, fix what is exploitable, prove each fix with a test, and report.Votes: 0GitHub stars: 234
- SpecFill the base and usecase spec templates from the interview answers, and list what is still undecided.Votes: 0GitHub stars: 234
- UiBuild the spec's screens in Vue and connect them to the API.Votes: 0GitHub stars: 234
- Acceptance CloudflareProve each must-have from the spec works end to end inside the Workers runtime, one test per must-have.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
- Actions CloudflareBuild the source's actions and ingests the spec decided to build as Worker features, and write down the ones left to a person.Votes: 0GitHub stars: 234
- Actions FirebaseBuild the source's actions and ingests the spec decided to build, on Firebase, and write down the ones left to a person.Votes: 0GitHub stars: 234
- ActionsBuild the source's actions and ingests the spec decided to build, and write down the ones left to a person.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
- Import CloudflareMove the copied collection's records into D1 and the files they point at into R2, proven on a fresh local state.Votes: 0GitHub stars: 234
- Import FirebaseBuild the import that moves the copied records into Firestore and their files into Cloud Storage, and prove it on the emulators.Votes: 0GitHub stars: 234
- Import Production CloudflareAfter the publish, move the copied records and their files into the production D1 and R2 with the import proven locally.Votes: 0GitHub stars: 234
- ImportMove the copied collection's records, and the files they point at, into the app's database and data/files/.Votes: 0GitHub stars: 234
- ApplySet chaff up in the folder: chaff.yaml for the chosen genre, today's findings shelved in .chaff-baseline.json, and, when asked, a GitHub workflow that puts new findings on the pull request's lines.Votes: 0GitHub stars: 234
- SurveyMeasure what chaff reports on the named documents today, as the kind the person chose, and propose the setup — changing nothing yet.Votes: 0GitHub stars: 234
- PairPair every article of the old version with its article in the new one, and say whether each changed, was added or was removed — writing .blueprint/comparison.json and changing no document.Votes: 0GitHub stars: 234
- ReportWrite the comparison table of the two versions from the checked pairing, and what was checked.Votes: 0GitHub stars: 234
- Actions SupabaseBuild the source's actions and ingests the spec decided to build as Postgres functions and Supabase Edge Functions, and write down the ones left to a person.Votes: 0GitHub stars: 234
- Import Production SupabaseAfter the publish, move the copied records and their files into the production Postgres and Storage with the import proven locally.Votes: 0GitHub stars: 234
- Import SupabaseMove the copied collection's records into Postgres and the files they point at into Storage, proven on a freshly reset local database.Votes: 0GitHub stars: 234
- ApplyWhen the person asked, put the glossary's spellings and jargon into the folder's chaff.yaml without losing what it had; then write the glossary up for them.Votes: 0GitHub stars: 234
- CollectCollect the terms the documents define, the ways each word is spelled, and the jargon, each quoted where it was found, into .blueprint/glossary.json — changing no document.Votes: 0GitHub stars: 234
- Acceptance SupabaseProve each must-have works end to end against the local Supabase stack as the user the spec names, and is refused for everyone else.Votes: 0GitHub stars: 234
- ReportWrite the checked summary up for the person: the summary, where each sentence comes from, and what was left out.Votes: 0GitHub stars: 234
- SummarizeSummarize the named documents to the agreed length, one sentence at a time, each backed by quotations, citing every part or leaving it out with a reason — writing .blueprint/summary.json and changing no document.Votes: 0GitHub stars: 234
- AuthAdd the spec's sign-in with Supabase Auth, open sign-up only as far as the spec says, and prove it.Votes: 0GitHub stars: 234
- DataTurn the spec's tables into Postgres migrations with row level security for every read and write, a seed, and tests per kind of user.Votes: 0GitHub stars: 234
- DeployWith approval, apply the migrations to the person's Supabase project and publish the screen, built for that project, on Cloudflare.Votes: 0GitHub stars: 234
- HandoverWrite the README and the first page for the person: where the app is, how to run and change it, how to back up the data.Votes: 0GitHub stars: 234
- PrerequisitesConfirm Node 22 or later, yarn, and a running Docker Desktop for the local Supabase stack.Votes: 0GitHub stars: 234
- Run CheckStart the app on this computer against the local Supabase stack and fix what only breaks in the built version.Votes: 0GitHub stars: 234
- ScaffoldLay out a Vue app on the local Supabase stack, served as static files by wrangler, with tests that run against the local stack.Votes: 0GitHub stars: 234
- SecurityReview the built app against OWASP Top 10:2025 as an attacker would, fix what is exploitable, prove it on the local stack, and write the report.Votes: 0GitHub stars: 234
- UiBuild the spec's screens in Vue, reading and writing Supabase from the browser.Votes: 0GitHub stars: 234
- DesignGive the screens the look the user chose: MulmoTerminal's own collection screens, or a design template on the same classes.Votes: 0GitHub stars: 234