.agents/skills/self-improvement-debt-tracker/SKILL.md
Track technical debt tasks for the development-orchestrator skill.
npx skillsauth add em-jones/staccato-toolkit self-improvement-debt-trackerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Track technical debt tasks for the development-orchestrator skill.
Purpose: Create tasks in an "agent-tech-debt" epic whenever errors occur or large token parsing operations are needed.
When an error occurs during development-orchestrator execution:
Capture error context:
Create technical debt task:
td create "Fix: <error-summary>" --type task --epic agent-tech-debt \
--body "**Error occurred during:** <phase>\n\n**Change:** <change-name>\n\n**Error details:**\n\n```
<error-message>\n <stack-trace>\n \n\n**Context:**\n- Phase: <phase>\n- Change: <change-name>\n- Timestamp: <timestamp>\n\n**Sample:**\n\n<error-sample>\n```"
Link to relevant artifacts:
When parsing large amounts of tokens (detected by token count or processing time):
Capture parsing context:
Create optimization task:
td create "Optimize: <operation-description>" --type task --epic agent-tech-debt \
--body "**Large token parsing detected during:** <phase>\n\n**Operation:** <description>\n\n**Metrics:**\n- Estimated tokens: <count>\n- Duration: <time>\n- Phase: <phase>\n\n**Context:**\n- Change: <change-name>\n- Timestamp: <timestamp>\n\n**Sample:**\n```\n<operation-sample>\n```"
Link to relevant files:
Epic creation: Ensure "agent-tech-debt" epic exists:
td epic create "agent-tech-debt" --desc "Technical debt tasks for agent improvements"
Task prioritization: All tasks default to medium priority
Task assignment: Tasks are unassigned (agent will handle them)
Task tracking: Tasks remain in "agent-tech-debt" epic until resolved
This skill integrates with development-orchestrator at these points:
Error scenario:
# During artifact authoring, a template fails to render
# Skill creates task:
td create "Fix: template rendering failure" --type task --epic agent-tech-debt \
--body "**Error occurred during:** artifact authoring\n\n**Change:** add-user-auth\n\n**Error details:**\n\n```\nTemplate rendering failed: invalid syntax in template file\nStack trace: ...\n```\n\n**Context:**\n- Phase: artifact authoring\n- Change: add-user-auth\n- Timestamp: 2026-02-24T10:30:00Z\n\n**Sample:**\n```\nTemplate error: unexpected token in template file\n```"
Large token parsing scenario:
# During design phase, parsing 50k+ token design document
# Skill creates task:
td create "Optimize: large design document parsing" --type task --epic agent-tech-debt \
--body "**Large token parsing detected during:** design phase\n\n**Operation:** parsing design.md with 50,000+ tokens\n\n**Metrics:**\n- Estimated tokens: 50,000+\n- Duration: 15 seconds\n- Phase: design\n\n**Context:**\n- Change: add-user-auth\n- Timestamp: 2026-02-24T10:45:00Z\n\n**Sample:**\n```\nParsing design.md took 15 seconds with 50,000+ tokens\n```"
This skill is only active when:
Relative paths in this skill (e.g., scripts/, reference/) are relative to this base directory. Note: file list is sampled.
<skill_files>
</skill_files>
tools
<!--VITE PLUS START--> # Using Vite+, the Unified Toolchain for the Web This project is using Vite+, a unified toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite, but it invokes Vite through `vp dev` and `vp build`. ## Vite+ Workflow `vp` is a global binary that handles the full development lifecycle. Run `vp help` to pr
development
Guide for building performant data tables. Uses tanstack-table for table logic (sorting, filtering, pagination) and tanstack-virtual for rendering large datasets efficiently.
development
Expert guidance for building observable, expressive, and fault-tolerant TypeScript applications using the effect-ts/effect ecosystem. Covers Effect<A, E, R> type, error management, dependency injection via Layers, observability (logging, metrics, tracing), concurrency with Fibers, retry/scheduling, Schema validation, Streams, and Sinks.
tools
Complete E2E (end-to-end) and integration testing skill for TypeScript/NestJS projects using Jest, real infrastructure via Docker, and GWT pattern. ALWAYS use this skill when user needs to: **SETUP** - Initialize or configure E2E testing infrastructure: - Set up E2E testing for a new project - Configure docker-compose for testing (Kafka, PostgreSQL, MongoDB, Redis) - Create jest-e2e.config.ts or E2E Jest configuration - Set up test helpers for database, Kafka, or Redis - Configure .env.e2e environment variables - Create test/e2e directory structure **WRITE** - Create or add E2E/integration tests: - Write, create, add, or generate e2e tests or integration tests - Test API endpoints, workflows, or complete features end-to-end - Test with real databases, message brokers, or external services - Test Kafka consumers/producers, event-driven workflows - Working on any file ending in .e2e-spec.ts or in test/e2e/ directory - Use GWT (Given-When-Then) pattern for tests **REVIEW** - Audit or evaluate E2E tests: - Review existing E2E tests for quality - Check test isolation and cleanup patterns - Audit GWT pattern compliance - Evaluate assertion quality and specificity - Check for anti-patterns (multiple WHEN actions, conditional assertions) **RUN** - Execute or analyze E2E test results: - Run E2E tests - Start/stop Docker infrastructure for testing - Analyze E2E test results - Verify Docker services are healthy - Interpret test output and failures **DEBUG** - Fix failing or flaky E2E tests: - Fix failing E2E tests - Debug flaky tests or test isolation issues - Troubleshoot connection errors (database, Kafka, Redis) - Fix timeout issues or async operation failures - Diagnose race conditions or state leakage - Debug Kafka message consumption issues **OPTIMIZE** - Improve E2E test performance: - Speed up slow E2E tests - Optimize Docker infrastructure startup - Replace fixed waits with smart polling - Reduce beforeEach cleanup time - Improve test parallelization where safe Keywords: e2e, end-to-end, integration test, e2e-spec.ts, test/e2e, Jest, supertest, NestJS, Kafka, Redpanda, PostgreSQL, MongoDB, Redis, docker-compose, GWT pattern, Given-When-Then, real infrastructure, test isolation, flaky test, MSW, nock, waitForMessages, fix e2e, debug e2e, run e2e, review e2e, optimize e2e, setup e2e