dayfinggg
- 42 skills
- 0 followers
- 8 repo stars
- 2 days ago last updated
- ▌ Python · dayfinggg bundleGives current Python practice for uv, ruff, ty, and pytest, with Django and FastAPI references. Use it whenever you write, review, upgrade, or set up Python code, including dependencies, virtual environments, scripts, linting, formatting, type checking, and pytest tests. Use it for every Django or FastAPI change, because it routes to framework references.
- ▌ Review 2 · dayfingggReviews a change with fresh reviewers that did not write it, for bugs and security problems, for breaches of the repo's documented coding standards, and for gaps against what was asked. Use when the user asks for a review, before opening a pull request, and before you report as done a change that is large or hard to undo, such as one that spans several modules or touches data, security, or a production system.
- ▌ Wizard · dayfinggg bundleGenerates an interactive bash wizard that walks a human through steps only they can perform. Use when a person must provision infrastructure, create credentials or CI secrets, or click through a third-party dashboard. Use for a one-off migration or cutover with manual steps. Skip it for steps the agent can perform itself.
- ▌ Handoff 2 · dayfingggCompacts the current conversation into a handoff document that a fresh agent or session can pick up. Use when the user wants to continue the work in a new session or hand it to another agent.
- ▌ Testing · dayfinggg bundlePicks the check that proves a change works and the test level for it, and routes to procedures for browser, CLI, API, contract, and flaky tests. Use it when the project gives no obvious check for the change, when you review or repair existing tests, for UI changes checked in a browser, for HTTP APIs and command-line tools, and when a test fails only sometimes. Running a test command the project already documents needs no skill, and the `tdd` skill covers writing a new test first.
- ▌ Database · dayfinggg bundleGuides safe, current database work on PostgreSQL and MySQL. Use it whenever a task touches a database, such as schema changes, migrations, queries, ORM code, data fixes, imports, backfills, or deletes. Use it before any command that resets, drops, truncates, or wipes data, or that connects to a production database.
- ▌ Planning · dayfingggBreaks work into ordered, verifiable tasks before implementation. Use it whenever the user asks for a plan, a roadmap, or an estimate, when requirements or a spec must become tasks, when the work spans several modules, sessions, or agents, or when a task feels too large or vague to start. Skip it for a change whose scope and order are already obvious.
- ▌ Research · dayfingggFinds and verifies current facts in official docs, source code, and the web, and cites each claim with a deep link. Use it whenever an answer depends on a framework, library, API, service, price, or rule that changes over time, before writing framework-specific code from memory, when comparing tools or options, and when the user asks for research or for a comparison or report that rests on sources.
- ▌ Agentdocs · dayfinggg bundleGuides the writing and audit of documents that agents read. Use when creating, editing, or reviewing a skill, its description, or its reference files, and when writing or modifying AGENTS.md, CLAUDE.md, a rule file, or a doc that an agent reaches through a pointer.
- ▌ Cleancode · dayfinggg bundleRoutes code quality work to compressed rules from Code Complete, Refactoring, Working Effectively with Legacy Code, and Release It. Use it when you write a new module or a sizeable piece of logic, when the task is a refactor or cleanup, when you change code that lacks trustworthy tests, and when you add outbound calls, retries, queues, background jobs, migrations, or deploy steps. A small edit inside existing code needs only the coding instructions.
- ▌ Debugging · dayfinggg bundleDiagnosis loop for anything reported broken, throwing, failing, flaky, slow, or giving wrong output, including a user's report that a feature or page stopped working. Use it whenever such a report arrives and the cause is not yet proven by the error and the code it points to, before you change code to fix it, even when the first explanation looks obvious.
- ▌ Prototype · dayfinggg bundleBuilds a throwaway prototype that answers one design question. Use when the user wants to check whether a state model, business rule, or data shape feels right before building. Use when the user wants to compare designs for a page, screen, or component before committing to one.
- ▌ Delegation · dayfingggPicks the provider, model, and effort for another agent and writes its complete brief. Use it before the first subagent, child task, or parallel agent of a task, whenever the user asks to delegate, parallelize, or run agents, and before handing work to a model of another provider.
- ▌ Javascript · dayfinggg bundleApplies current JavaScript, browser, and React practice, with performance rules ranked by impact. Use it whenever you write, review, or refactor JavaScript or JSX, React components, hooks, or Server Components, or a Next.js app. Use it when fixing slow pages, request waterfalls, large bundles, extra re-renders, layout thrashing, or hydration mismatches. Use it when choosing a recent ECMAScript feature for the project's target runtimes.
- ▌ Typescript · dayfinggg bundleWrites and fixes TypeScript types and compiler settings. Use it whenever a task adds or changes types, generics, type guards, branded types, or utility types, and when tsc reports a type error. Use it to replace `any` with a strict type. Use it when editing tsconfig.json, choosing module, target, or resolution settings, or upgrading to TypeScript 6 or 7 with the Go-based native compiler.
- ▌ Git · dayfinggg bundleStructures git workflow and pull request bodies. Use it when committing, branching, pushing, resolving conflicts, splitting uncommitted work into atomic commits, opening a pull request (PR), or cutting a release with a version bump, a tag, or a changelog. Use it for a commit message, a PR description, or a changelog entry, even when the diff is pasted inline and the message looks easy to write.
- ▌ PHP · dayfinggg bundleGives current PHP practice for language features, Composer, static analysis, and tests, with Laravel and Symfony references. Use it whenever you write, review, upgrade, or set up PHP code, including Composer packages, PHPStan or Rector configuration, and PHPUnit or Pest tests. Use it for every Laravel or Symfony change, because it routes to framework references for Eloquent, validation, queues, testing, Doctrine, Messenger, forms, and voters.
- ▌ Tdd 2 · dayfinggg bundleGuides test-first work through a failing test and the smallest change that passes it, with tests placed at public seams. Use it before you write a new test for a feature or a bug fix, including a regression test, and when the user asks for test-first work, TDD, or red-green-refactor. The `testing` skill covers which check a change needs and the repair of existing tests.
- ▌ Node · dayfinggg bundleGives current Node.js runtime practice. Use it whenever you write, review, or debug Node.js servers, CLIs, workers, or scripts. Use it for streams, async code, errors, logging, caching, environment config, and graceful shutdown. Use it for flaky or hanging tests with node:test, for profiling, and for running TypeScript directly in Node. Use it when choosing Node APIs for the installed version or upgrading Node.
- ▌ Grill · dayfingggInterviews the user in rounds of questions until a plan, decision, or idea is fully thought through. Use when the user asks to stress-test, challenge, or be grilled on their own plan, design, decision, or idea. Skip it when the user only wants an answer, a recommendation, or the work done.
- ▌ Design · dayfinggg bundleVocabulary and method for designing deep modules, which hide a lot of behavior behind a small interface at a clean seam. Use it when you decide or change a module's interface or the boundary between parts, place a seam, make code testable, merge shallow modules, or compare interface designs. A class added inside an existing design needs no skill.
- ▌ Domain · dayfinggg bundleBuilds and sharpens a project's domain model as design work happens. Use when a discussion turns on codebase terminology, or when a term is vague, overloaded, or against the glossary. Use when writing or editing a GLOSSARY.md. Use when recording or editing an architecture decision record (ADR).
- ▌ Tdd · dayfinggg bundleDevelop a feature or bug fix through a focused failing-test, minimal-implementation, and refactor loop. Use when the user requests TDD, asks for a regression test, or the bug has an obvious cheap local test target. Do not force TDD when the useful test path is unclear, expensive, or integration-heavy.
- ▌ Scout · dayfinggg bundleMap an unfamiliar codebase, trace runtime flow, locate ownership, and identify the files that matter. Use for codebase orientation, onboarding, placement questions, and investigation before planning. This is a read-only skill and does not design or implement changes.
- ▌ Swarm · dayfinggg bundleFan out several independent investigations or candidate solutions and synthesize them into one judged result. Use when parallel agents are authorized by the user or governing instructions and independent investigations materially benefit from them. Do not use for dependent steps or shared mutable state.
- ▌ Impact · dayfinggg bundleDetermine what a proposed or completed change could break outside its immediate diff. Use for blast-radius analysis, shared contracts, migrations, risky refactors, and changes to public interfaces or persistent data. Do not use for a general code review with no cross-boundary risk.
- ▌ Review · dayfinggg bundleReview a diff, branch, pull request, or work-in-progress change for correctness, requirement fit, regressions, and maintainability. Use when the user asks for code review or assessment of completed changes. Report findings without editing unless a fix is also requested.
- ▌ Triage · dayfinggg bundleClassify an incoming issue, bug report, alert, or external pull request and turn it into an actionable engineering brief. Use when work needs validation, priority, ownership, or missing-information assessment before implementation. Do not solve the issue unless separately requested.
- ▌ Verify · dayfinggg bundleProve that completed engineering work satisfies its requirements using the real artifact, focused tests, and diff inspection. Use before declaring implementation complete or when the user asks whether a change actually works. Do not replace diagnosis or code review.
- ▌ Context · dayfinggg bundleAssemble the smallest trustworthy context needed for an active engineering task. Use when resuming long work, switching subsystems, handing work between agents, or when stale or excessive context is degrading decisions. Do not activate for a small self-contained request.
- ▌ Handoff · dayfinggg bundleTransfer active engineering work to another agent or session without losing decisions, evidence, or the next executable step. Use when the user requests a handoff, work must continue elsewhere, or context limits threaten continuity. Do not use as a generic session summary.
- ▌ Journal · dayfinggg bundleMaintain a compact evidence-backed decision trail for long-running, unattended, or high-risk engineering work. Use when later reviewers must understand what changed, why, and what proved it. Do not activate for routine short tasks or duplicate ordinary progress narration.
- ▌ Migrate · dayfinggg bundleMove code, callers, data, configuration, or dependencies from an old contract to a new one with explicit compatibility and rollback decisions. Use for API, schema, framework, dependency, or storage migrations. Do not use for a simple isolated replacement with no consumers.
- ▌ Reflect · dayfinggg bundleExtract reusable, evidence-supported improvements after a completed engineering session, repeated failure, or explicit retrospective request. Use when the goal is to improve future agent behavior or an existing workflow. Do not activate automatically after every task or create new rules from a single preference.
- ▌ Roadmap · dayfinggg bundleBreak a large or multi-session engineering objective into ordered, verifiable stages with dependencies and checkpoints. Use when the user asks for an implementation plan or complex authorized work needs internal sequencing. Do not turn an implementation request into a planning-only response.
- ▌ Specify · dayfinggg bundleTurn settled requirements or an existing conversation into an implementation-ready specification with testable behavior and explicit scope. Use when the desired outcome is mostly known and needs consolidation. Do not use for open-ended discovery or implementation.
- ▌ Delegate · dayfinggg bundlePrepare and assign one bounded, independently verifiable subtask to a subagent. Use when delegation is authorized by the user or governing instructions, collaboration tools are available, and one independent work unit will materially help. Do not use merely to avoid doing a small task locally.
- ▌ Diagnose · dayfinggg bundleReproduce a failure, regression, or performance problem and identify its root cause with evidence. Use when the user asks why something is broken, failing, crashing, flaky, or slow. Do not modify the implementation unless the request also asks for a fix.
- ▌ Refactor · dayfinggg bundleSimplify existing code, improve module depth, or reduce reader load while preserving observable behavior. Use when the user explicitly requests restructuring or when a behavior-preserving cleanup is the task. Do not activate for ordinary feature work that merely touches imperfect code.
- ▌ Architect · dayfinggg bundleDesign types, interfaces, module boundaries, and ownership for a non-trivial feature or structural change. Use when an early choice affects several components. Skip small local edits and settled designs.
- ▌ Implement · dayfinggg bundleMake an authorized code or configuration change from a settled request, specification, or task. Use when the user asks to build, fix, add, or change something and the implementation scope is clear. Do not use for diagnosis-only, review-only, or planning-only requests.
- ▌ Standards · dayfinggg bundleApply relevant code, test, database, and interface standards during implementation or review. Detect the installed stack and load only guidance needed for the changed behavior. Do not use for prose-only tasks or unrelated audits.