datit309

@datit309 source repo

25 skills
0 followers
19 hours ago last updated

▌
Supergraph · datit309 bundle
Meta-orchestrator — dispatches to the right skill for the task. Use before any non-trivial work.

0
installs
▌
Fix · datit309
Plan-aware auto-fix loop after coding. Runs tests, lint, format, and graph checks. Updates plan task status. Use after execute/tdd.

0
installs
▌
Prd · datit309
Convert current conversation context into a structured Product Requirements Document (PRD) and optionally post it to GitHub Issues. Use before /supergraph:plan when requirements came from a conversation, user story, or feature discussion rather than a formal spec.

0
installs
▌
Sdd · datit309
Create a Software Design Document (SDD) defining component architecture, data contracts, API schemas, and platform compatibility before planning. Use in Tier 3 (Full Pipeline) or when modifying interfaces, hooks, databases, or multi-platform contracts.

0
installs
▌
Tdd · datit309
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.

0
installs
▌
Plan · datit309
Create graph-informed implementation plans before writing code. Use before any non-trivial task. Skip for small changes (≤2 files, <20 lines, no hub/bridge).

0
installs
▌
Scan · datit309
Scan project once per session. Run first — all other skills depend on this.

0
installs
▌
Review · datit309
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.

0
installs
▌
Serena · datit309
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.

0
installs
▌
Triage · datit309
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for automation.

0
installs
▌
Verify · datit309
Fresh verification gate before claiming done, fixed, passing, ready, or before commit/PR. Evidence before claims, always.

0
installs
▌
Analyze · datit309
Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.

0
installs
▌
Caveman · datit309
Persistent token-compression mode (~75% reduction) — now always-on by default. Strips filler while keeping code exact.

0
installs
▌
Execute · datit309
Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.

0
installs
▌
Handoff · datit309
Compact current session context into a handoff document for seamless continuation in a new session. Use when context window is exhausted, switching machines, handing work to another agent, or ending a long session mid-task.

0
installs
▌
Diagnose · datit309
Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.

0
installs
▌
Zoom Out · datit309
One-shot module map — go up a layer of abstraction and get a domain-vocabulary module map of the codebase. Use when lost in unfamiliar code, after a long deep-dive session, or when you need to re-orient before planning.

0
installs
▌
Prototype · datit309
Build throwaway code to validate an uncertain approach before committing to a plan. Two branches — Logic (terminal state machine) or UI (multiple designs on one route with URL-param switcher). No persistence, no tests, single-command start. Use between analyze and plan when the approach itself is uncertain.

0
installs
▌
Flutter UI · datit309
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.

0
installs
▌
Integration · datit309
Run integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.

0
installs
▌
Architecture · datit309
Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.

0
installs
▌
Webapp Testing · datit309 bundle
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

0
installs
▌
Frontend Design · datit309
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

0
installs
▌
Database Migrations · datit309 bundle
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

0
installs
▌
Flutter Dart Code Review · datit309 bundle
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.

0
installs

25 published skills