All authors
Claude Skills by Fadi88
github.com/Fadi8854 skills0 installs2 views
- Bug FixFix a bug test first - reproduce it in a failing test, fix, watch the test pass, and stop after three failed attempts to rethink. Use for any reported bug or failing behaviour.Votes: 0GitHub stars: 2
- CommitCommit discipline - one change per commit, the founder as the only author, requirement ids in the subject, no tool or model credited, hooks never bypassed. Use whenever a commit is made.Votes: 0GitHub stars: 2
- Context BudgetHow to spend context - open what the task names, grep before reading, read ranges, prefer a checker's output, say what was opened. Use on every task; it is what keeps a long change from losing its own thread halfway.Votes: 0GitHub stars: 2
- Cost AuditThe optimizer's method for finding cost and waste in the agent workflow - model tier per agent, context loaded per step, redundant and skipped steps, slow or useless checks - and proposing ranked, reversible cuts. Use monthly, on a spend jump, or when the founder asks why something was slow or expensive.Votes: 0GitHub stars: 2
- Decision LogWhere decisions live and who makes them - open questions, closed decisions, rejected proposals - so the team never re-argues a settled point or decides something that is the founder's. Use when a decision is needed, taken, deferred or challenged.Votes: 0GitHub stars: 2
- ExperimentRun every bet, growth idea or workflow change as a pre-registered experiment - hypothesis, the number that would prove it, a read date, and what result would make it wrong - written before it starts. Use for pricing, copy, onboarding, channels, cost cuts and any \"let's try\".Votes: 0GitHub stars: 2
- Frontend DesignDistinctive, intentional visual design for any UI being built or reshaped - aesthetic direction, typography, layout, motion and interface copy that does not read as a templated default. Use on every ticket that changes what users see.Votes: 0GitHub stars: 2
- GatesWhat each gate level (strict, standard, light) switches on and off, and what never relaxes at any level. Use when setup asks the founder to choose a level, when the level changes, and whenever an agent is unsure whether a step is required.Votes: 0GitHub stars: 2
- Grill MeThe founder's command to be interviewed hard about a plan or idea. Runs the grilling skill on whatever the founder names.Votes: 0GitHub stars: 2
- GrillingInterview the founder relentlessly about a plan, feature or decision until there is a shared understanding with nothing silently assumed. Used by setup, new-feature and bets, or whenever the founder says grill.Votes: 0GitHub stars: 2
- HandoffThe format for passing work between agents - a brief going out, a short report with file paths coming back. Use for every delegation and every hand-back.Votes: 0GitHub stars: 2
- Human StepsTurn the steps only the founder can do (accounts, domains, payments, store listings, secrets, signatures) into a numbered script they follow, with a check after each step. Use whenever work is blocked on something an agent must not or cannot do.Votes: 0GitHub stars: 2
- Karpathy GuidelinesBehavioural guidelines that reduce common AI coding mistakes - think before coding, simplicity first, surgical changes, goal-driven execution. Use on every task that writes or changes code.Votes: 0GitHub stars: 2
- Known RedsThe register of failing checks the founder has decided to live with for now, each matched by its failing line, owned and dated. Use when a red is accepted, rechecked or fixed.Votes: 0GitHub stars: 2
- Legal ReviewThe legal agent's method - read the founder's playbook and the region packs, grade each checklist item GREEN, YELLOW, RED or UNSETTLED with a cited and dated source, draft documents flagged for counsel, escalate. Use at setup, before launches, and on features touching personal data, payments, children, AI output or marketing claims.Votes: 0GitHub stars: 2
- New FeatureThe intake for any feature a user would notice - grill the founder, write the spec and requirement rows, pass the readiness gate, then route design, build, QA and reviews. Use whenever the founder asks for something new.Votes: 0GitHub stars: 2
- Ordered StepsOutward and irreversible actions wait for the founder's explicit go, one step at a time - \"do X, then deploy\" means show X and stop. Use before any deploy, merge, push, publish, send, payment, deletion or production data change.Votes: 0GitHub stars: 2
- Readiness GateThe checklist a feature must pass before any build starts - spec confirmed, rows written, no open question on the path, constitution respected. Use before handing any ticket to a developer agent.Votes: 0GitHub stars: 2
- ReleaseThe release checklist - QA pass, reviews in, rollback written, backup tested, then merge, migrate, deploy and announce, each on the founder's go - and the watch after. Use for every release to users.Votes: 0GitHub stars: 2
- Requirement FirstHow requirement rows are written, numbered, statused and cited - the row comes before the code. Use before any change to code, copy or config, and whenever a requirement id is mentioned.Votes: 0GitHub stars: 2
- Safe Data WriteHow any write to real user or business data proves itself and stays reversible - before-image journal, read-back proof that the target changed and nothing else did, undo by change id. Use for every write, migration, backfill or bulk edit on real data.Votes: 0GitHub stars: 2
- SetupThe setup interview that customises this template for one founder's company by region, domain, audience, customer size, stack, gates, team and budget, and writes project.toml. Use at the start of a new company or when any of those change.Votes: 0GitHub stars: 2
- Single SourceEvery derived figure (a total, a price, a score, a status) is computed in exactly one place and read everywhere; documents never carry hand-typed counts. Use when adding any number a user or the founder will see.Votes: 0GitHub stars: 2
- Spec AuditCheck whether a feature or codebase is specified well enough to hand to a developer agent - five layers (what it does, its interfaces, its architecture, how it ages, what good looks like here) - and name the decisions an agent would otherwise fill in silently. Use before the readiness gate on any feature that touches existing code, and at setup when a codebase already exists.Votes: 0GitHub stars: 2
- Twin CheckGuard important business arithmetic with an independent, dependency-free reference implementation checked against the production code's real output. Use for prices, billing, quotas, scores, forecasts - any figure where a wrong answer still looks like an answer.Votes: 0GitHub stars: 2
- Verified ClaimsNo unconfirmed assumptions - every factual claim the founder or a user will read is confirmed by a source, test or measurement, or cut, or registered in docs/ASSUMPTIONS.md and labelled. Use when writing any document, copy, report, estimate or recommendation, and when reviewing one.Votes: 0GitHub stars: 2
- Verify GreenRun what covers a change, then the full sweep, and end every round green - and who owns a red. Use before handing any work back, before any commit, and whenever a check fails.Votes: 0GitHub stars: 2
- Bug FixFix a bug test first - reproduce it in a failing test, fix, watch the test pass, and stop after three failed attempts to rethink. Use for any reported bug or failing behaviour.Votes: 0GitHub stars: 2
- CommitCommit discipline - one change per commit, the founder as the only author, requirement ids in the subject, no tool or model credited, hooks never bypassed. Use whenever a commit is made.Votes: 0GitHub stars: 2
- Context BudgetHow to spend context - open what the task names, grep before reading, read ranges, prefer a checker's output, say what was opened. Use on every task; it is what keeps a long change from losing its own thread halfway.Votes: 0GitHub stars: 2
- Cost AuditThe optimizer's method for finding cost and waste in the agent workflow - model tier per agent, context loaded per step, redundant and skipped steps, slow or useless checks - and proposing ranked, reversible cuts. Use monthly, on a spend jump, or when the founder asks why something was slow or expensive.Votes: 0GitHub stars: 2
- Decision LogWhere decisions live and who makes them - open questions, closed decisions, rejected proposals - so the team never re-argues a settled point or decides something that is the founder's. Use when a decision is needed, taken, deferred or challenged.Votes: 0GitHub stars: 2
- ExperimentRun every bet, growth idea or workflow change as a pre-registered experiment - hypothesis, the number that would prove it, a read date, and what result would make it wrong - written before it starts. Use for pricing, copy, onboarding, channels, cost cuts and any "let's try".Votes: 0GitHub stars: 2
- Frontend DesignDistinctive, intentional visual design for any UI being built or reshaped - aesthetic direction, typography, layout, motion and interface copy that does not read as a templated default. Use on every ticket that changes what users see.Votes: 0GitHub stars: 2
- GatesWhat each gate level (strict, standard, light) switches on and off, and what never relaxes at any level. Use when setup asks the founder to choose a level, when the level changes, and whenever an agent is unsure whether a step is required.Votes: 0GitHub stars: 2
- Grill MeThe founder's command to be interviewed hard about a plan or idea. Runs the grilling skill on whatever the founder names.Votes: 0GitHub stars: 2
- GrillingInterview the founder relentlessly about a plan, feature or decision until there is a shared understanding with nothing silently assumed. Used by setup, new-feature and bets, or whenever the founder says grill.Votes: 0GitHub stars: 2
- HandoffThe format for passing work between agents - a brief going out, a short report with file paths coming back. Use for every delegation and every hand-back.Votes: 0GitHub stars: 2
- Human StepsTurn the steps only the founder can do (accounts, domains, payments, store listings, secrets, signatures) into a numbered script they follow, with a check after each step. Use whenever work is blocked on something an agent must not or cannot do.Votes: 0GitHub stars: 2
- Karpathy GuidelinesBehavioural guidelines that reduce common AI coding mistakes - think before coding, simplicity first, surgical changes, goal-driven execution. Use on every task that writes or changes code.Votes: 0GitHub stars: 2
- Known RedsThe register of failing checks the founder has decided to live with for now, each matched by its failing line, owned and dated. Use when a red is accepted, rechecked or fixed.Votes: 0GitHub stars: 2
- Legal ReviewThe legal agent's method - read the founder's playbook and the region packs, grade each checklist item GREEN, YELLOW, RED or UNSETTLED with a cited and dated source, draft documents flagged for counsel, escalate. Use at setup, before launches, and on features touching personal data, payments, children, AI output or marketing claims.Votes: 0GitHub stars: 2
- New FeatureThe intake for any feature a user would notice - grill the founder, write the spec and requirement rows, pass the readiness gate, then route design, build, QA and reviews. Use whenever the founder asks for something new.Votes: 0GitHub stars: 2
- Ordered StepsOutward and irreversible actions wait for the founder's explicit go, one step at a time - "do X, then deploy" means show X and stop. Use before any deploy, merge, push, publish, send, payment, deletion or production data change.Votes: 0GitHub stars: 2
- Readiness GateThe checklist a feature must pass before any build starts - spec confirmed, rows written, no open question on the path, constitution respected. Use before handing any ticket to a developer agent.Votes: 0GitHub stars: 2
- ReleaseThe release checklist - QA pass, reviews in, rollback written, backup tested, then merge, migrate, deploy and announce, each on the founder's go - and the watch after. Use for every release to users.Votes: 0GitHub stars: 2
- Requirement FirstHow requirement rows are written, numbered, statused and cited - the row comes before the code. Use before any change to code, copy or config, and whenever a requirement id is mentioned.Votes: 0GitHub stars: 2
- Safe Data WriteHow any write to real user or business data proves itself and stays reversible - before-image journal, read-back proof that the target changed and nothing else did, undo by change id. Use for every write, migration, backfill or bulk edit on real data.Votes: 0GitHub stars: 2
- SetupThe setup interview that customises this template for one founder's company by region, domain, audience, customer size, stack, gates, team and budget, and writes project.toml. Use at the start of a new company or when any of those change.Votes: 0GitHub stars: 2
- Single SourceEvery derived figure (a total, a price, a score, a status) is computed in exactly one place and read everywhere; documents never carry hand-typed counts. Use when adding any number a user or the founder will see.Votes: 0GitHub stars: 2