Results for “data-structure”

Use when creating tags, categories, or organizational structures for knowledge, documentation, or data. This skill provides consistent taxonomy standards across all companies and agents, enabling discoverability and cross-referencing.

Analyzes project folder structures, auto-detects technology stacks, and generates detailed blueprints with naming conventions, file placement patterns, and templates for consistent code organization.

Extracts specifications from existing codebases by analyzing structure, data flows, and observable behaviors to document requirements in EARS format.

Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration, documenting behavioral differences with severity, root cause, and remediation steps.

Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This skill operates in two phases — (1) generating a structured analysis framework with chapter skeleton, data query requirements, and analysis logic, and (2) after data collection by other skills, producing the final consulting-grade report with structured narratives, embedded charts, and strategic insights.

ALWAYS activate this skill. Apply these rules to every task regardless of domain. This skill governs how Claude Code verifies information, writes code, references documentation, and avoids fabricating functions, arguments, APIs, file paths, data structures, or facts. These rules override any inclination to guess.

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for writing documentation or architectural decision records.