Index of every page on this site: llms.txt
Avatar for Adi

Adi

Working at FaceIq Labs

12 skills 1 London, United Kingdom Synced

akdevsaha-dev/factory-skills

Collection of agent skills that I happen to use regularly.

12 skills 1
npx skilld add akdevsaha-dev/factory-skills --all
  • Explain what teammates changed in a shared Git repository since you last worked in it. Finds your last commit as the baseline, reads the real diffs and surrounding code, groups changes by feature, and flags what affects your current work, breaking changes, migrations, risks, and what to review. Read-only. Use when the user asks to catch up, what changed, what happened while they were away, what teammates did, what landed on main, or what a pull would bring in.

  • Deliver substantial engineering work end to end like a disciplined senior engineer. Plans only as much as the task needs, implements the smallest correct solution, verifies by actual impact, and reviews when risk justifies it. Use for large or high-risk work spanning several modules or systems, such as multi-system features, payments and financial workflows, matching or recommendation systems, onboarding and authorization, background jobs and integrations, or architectural changes. Accepts --effort snack, balanced (default), feast, or banquet. For a small, contained change, use implement-feature instead.

  • Implement a feature or behavior change in an existing codebase like a senior engineer. Inspects similar code first, reuses what exists, follows project conventions, adds meaningful tests, runs the project's checks, and reviews its own diff. Use when asked to implement, add, build, or extend a feature, endpoint, page, component, or workflow in an existing project.

  • Add production-grade authentication and authorization to an existing project with Supabase Auth, Clerk, or Better Auth, then verify it with adversarial tests. Use when the user asks to add, set up, initialize, or implement auth, authentication, authorization, login, sign-in, sign-up, OTP, social login, sessions, roles, permissions, or access control.

  • Initialize a production-oriented backend project using Node.js with TypeScript, Python with FastAPI and uv, or Go. Use when the user asks to initialize, scaffold, bootstrap, or set up a backend.

  • Connect an existing backend to a database using Prisma, Drizzle, or Supabase. Sets up config, the client, and environment variables without creating tables. Use when the user asks to initialize, set up, add, or connect a database.

  • Plan a substantial code change before implementing it. Grounds the request in the codebase, maps affected modules, contracts, consumers, data, and trust boundaries, assesses risk, and splits the work into small verifiable slices with acceptance criteria and a verification plan. Use when asked to plan, scope, design, or assess the impact of a change, before multi-module or high-risk work such as payments, authorization, migrations, integrations, or architectural changes.

  • Learn from a demonstrated engineering failure, such as a failed test, a confirmed review defect, a repeated mistake, a manual correction, or a regression. Finds the root cause, decides whether it is systematic, and proposes the smallest durable prevention (a test, lint rule, or tooling first; an instruction change last), validated against real examples. Never changes instructions or skills without explicit approval. Use when the same kind of mistake recurs, a defect escaped existing checks, or the user asks to learn from a failure.

  • Review a code change independently for correctness, security, contract safety, test adequacy, and maintainability, reporting only evidence-backed findings with exact locations and failure scenarios. Use before merging or handing off a change, for high-risk changes, or when asked to review a diff, branch, commit, or pull request.

  • Simplify recently changed code without changing its behavior. Removes unnecessary wrappers, speculative abstractions, redundant checks, dead code, and narrating comments, one change at a time, rerunning the affected checks after each. Use after implementing a change, when a diff feels heavier than the problem, or when asked to simplify, clean up, or reduce complexity in a change.

  • Turn local Git changes into clean atomic commits, verify them, push the branch to the user's fork, and open or update a GitHub pull request. Explicit invocation only; supports --dry-run, --draft, --no-pr, --no-push, and --skip-checks.

  • Verify a code change by what it actually affects, then run the checks for real. Traces the diff through contracts, consumers, data flow, and runtime to choose only the tests, API calls, migrations, and browser checks that matter, runs them narrow to broad, and reports evidence without overstating anything. Use after implementing a change, before review or merge, or when asked to test, verify, check, or prove that a change works.

Curated skills from @akdevsaha-dev. Checked GitHub just now