Agent Skills: canned-responses-step-1-define-the-use-case
Sub-skill of canned-responses: Step 1: Define the Use Case (+6).
ID: vamseeachanta/workspace-hub/canned-responses-step-1-define-the-use-case
177
Install this agent skill to your local
Skill Files
The files that make up canned-responses-step-1-define-the-use-case.
More agent skills
- ocr-document-processorExtract text and structure from scans, images, and scanned PDFs. Use for OCR, searchable PDFs, table extraction, receipt parsing, and business card parsing.
- working-with-legacy-codeSafely change and test untested codebases using Feathers'' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
- generate-translationsUse when new translation keys are added to packages to generate new translations strings
- remove-ai-slopsRemoves AI-generated code smells from branch changes or an explicit file list behind regression tests, including junk tests (prose pins, source greps, copied inventories, mock echoes), each proven by its class's rule before a cut. Use when the user asks to clean up, deslop, remove AI-slop patterns, or prune tests from recent changes.
- event-store-designDesign and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
- configuration-hardeningReview Talon tool placement and defensive prompts when requested or when adding or changing tools or subagents; apply confirmed changes and verify active capabilities.