tinyc0der
- 30 skills
- 0 followers
- 1 hour ago last updated
- ▌ Incremental Implementation · tinyc0derDelivers changes incrementally in thin, verifiable vertical slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step. Use when an Epic parent todo indexes child tracks so implementation must move to a child worktree rather than building the epic in the parent checkout.
- ▌ Git Workflow And Versioning · tinyc0derStructures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening, updating, or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
- ▌ Planning And Task Breakdown · tinyc0derBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. Use when an Epic parent needs child-track allocation and a parent todo that indexes children instead of duplicating their tasks.
- ▌ Verification And Validation · tinyc0derValidates completed changes against acceptance criteria and readiness gates. Use after implementation and before review, merge, or release to run final tests, build, lint, typecheck, integration and runtime checks and produce an evidence-based readiness verdict without adding production behavior.
- ▌ Debugging And Error Recovery · tinyc0derGuides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.
- ▌ Browser Testing With Devtools · tinyc0derTests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
- ▌ Constraint Driven Development · tinyc0der bundleEstablishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.
- ▌ Observability And Instrumentation · tinyc0derInstruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
- ▌ Verify Work · tinyc0derChecks completed work before handoff. Use when verifying a change or preparing evidence for review.
- ▌ Retrieve Context · tinyc0derResearches architecture options. Use when comparing designs for a new subsystem.
- ▌ Context Engineering · tinyc0derOptimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
- ▌ Shipping And Launch · tinyc0derPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
- ▌ CI CD And Automation · tinyc0derAutomates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
- ▌ Documentation And Adrs · tinyc0derRecords decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
- ▌ Security And Hardening · tinyc0derHardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.
- ▌ Code Review And Quality · tinyc0derConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
- ▌ Frontend UI Engineering · tinyc0derBuilds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
- ▌ Spec Driven Development · tinyc0derCreates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map, and when deciding whether that map stays on one Feature track or an Epic parent with child tracks.
- ▌ Test Case Design Review · tinyc0derDesigns and reviews automated test cases using the smallest risk-based set that gives meaningful regression confidence. Use when planning, writing, pruning, or reviewing unit, integration, end-to-end, or regression tests, especially when a suite risks becoming repetitive, implementation-coupled, or larger than the behavior warrants. Do not use to enforce test-first development or perform a general code review unrelated to tests.
- ▌ Test Driven Development · tinyc0derDrives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
- ▌ Doubt Driven Development · tinyc0derSubjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
- ▌ Performance Optimization · tinyc0derOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
- ▌ Deprecation And Migration · tinyc0derManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.
- ▌ Source Driven Development · tinyc0derGrounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
- ▌ Reflect · tinyc0derExamines agent sessions for harness corrections. Use when asked to reflect on a conversation, conduct a retrospective, or address recurring agent workflow friction.
- ▌ Delegate · tinyc0der bundleDelegates bounded engineering tasks and phases to Orca agent sessions with configurable runner choices. Use when the user asks for one-shot delegation, to coordinate phases across Codex, Grok, OpenCode, or Antigravity, to supervise a mixed-agent workflow, or to run delegate on a task.
- ▌ Idea Refine · tinyc0der bundleRefines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".
- ▌ Interview Me · tinyc0derExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
- ▌ Memory Management · tinyc0derMaintains running track notes, shared Open Knowledge Format (OKF) document metadata, and durable knowledge bundles. Use when recording ad hoc observations or skill and workflow improvement ideas, resuming a tracked change, formatting capability specs and track documents, saving verified lessons or preferences, or bootstrapping, pruning, and syncing memory.
- ▌ Using Agent Skills · tinyc0derDiscovers and invokes agent skills and selects workflows for engineering requests. Use when starting a session, choosing the skill for an activity, deciding which workflow applies, or routing a scoped change through its lifecycle. Use when classifying work as a feature, bug, epic, or bounded task.