1.5천건 · 관련도순
Guides migration of existing codebases to Rust without unsafe code, covering architecture, implementation, testing, and output comparisons. It measures performance before and after optimization and produces an interactive HTML report documenting results and unresolved differences.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit an entire codebase for unnecessary complexity and dependencies. Receive a ranked list of code to delete, simplify, or replace with standard library and platform features, with file paths and estimated reductions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Read existing code to reconstruct system specifications, including architecture, data flows, APIs, and business rules. Produces documentation tied to code locations, separating observed behavior from inferences and questions that need clarification.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Routes requests about a codebase to the appropriate skill for mapping its structure, generating knowledge graphs, updating documentation, extracting lessons, or storing and recalling project knowledge for future planning.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review codebases, APIs, and tools for vulnerabilities using source evidence and bounded local checks. Produces supported findings with impact, priority, and focused fixes, and can create structured reports for explicitly requested full audits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze an existing codebase to identify reusable design patterns in components, services, APIs, styling, and refresh scheduling. Produces structured descriptions with representative code, conventions, dependencies, and adaptation notes for reuse or later conversion into skills.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a codebase for an external security review by defining goals, running static checks, improving test coverage, and removing unused code. Assemble the review scope, verified build instructions, diagrams, and documentation into a package for auditors.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a threat model that identifies valuable assets, attack entry points, potential threats, and mitigation priorities. Use source code and past vulnerabilities, an interview with the application owner, or a combination of both.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze business concepts in a codebase to map business areas and suggest service boundaries. Use Domain-Driven Design, an approach organized around business meaning, to classify responsibilities, assess how closely they belong together, and recommend clearer integration points.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Make AI truly understand large codebases: for multi-repository, multi-microservice projects that have evolved over years, run architecture reverse-engineering + a Graph RAG graph + multi-language AST to compress a huge codebase into a structured knowledge base, where every conclusion traces back to a code line and every relation carries a confidence label. Suited to projects with 10+ repositories or microservices that AI cannot understand globally by reading the code directly. Triggers: architecture analysis, architecture reverse-engineering, codebase knowledge base, code-to-knowledge, architecture wiki, large multi-repo codebase. Loaded on demand by the teamai discovery stub.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Architecture picture of a codebase: turn a repository into one readable, interface-level PlantUML architecture picture - packages or modules, the public symbols other units actually import, bounded import edges - and get it rendered to a single PNG a chat surface can show. Use when the user says: codebase-uml, codebase uml, uml, plantuml, uml diagram, class diagram, package diagram, module diagram.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "analyze this codebase", "document this service", "generate technical docs", "I inherited this code", "help me understand this system", "create docs for this project", "what does this system look like", "onboard me to this codebase", "this codebase has no docs", "visualize the architecture from code", or any explicit request to produce structured documentation or architecture diagrams from an existing codebase. Specifically optimized for AWS workloads (CDK, CloudFormation, Terraform) with source-of-truth citations. Do NOT activate for code reviews, single-function explanations, generating new code, or general coding tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use when the user says 'assess my codebase architecture', 'what direction should my codebase go', 'architecture compass', 'understand my architecture', 'audit architecture drift', 'architectural assessment', or 'help me understand what is wrong with my codebase'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Semantic codebase search, code indexing, and prompt enhancement via standalone CLI. Use when: (1) Semantic code search with natural language queries, (2) Code indexing for remote codebase retrieval, (3) Prompt enhancement with codebase context, (4) Before grep/find/glob operations for better accuracy, (5) Complex requirements clarification, (6) Large codebase navigation. Triggers: "search context", "enhance prompt", "find code that", "index project", "clarify requirements". IMPORTANT: Always use ace-tool BEFORE grep/find/glob for semantic-level code location.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Study unfamiliar codebases and produce evidence-backed knowledge artifacts. Use for repository orientation, architecture mapping, subsystem tracing, onboarding, or codebase documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Estimate the full development cost of an existing codebase from lines of code, architectural complexity, and team-composition overhead. Use for 'how much would this cost to build', 'what did this codebase cost', development-cost or build-cost estimates, calendar-time estimates, and Claude/AI ROI on a delivered codebase. Estimates by measured LOC and complexity, not by ticket volume.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate onboarding documentation for a codebase — architecture overview, key files, local setup, and common gotchas. Use this skill whenever someone asks to onboard onto a codebase, create onboarding docs, generate a codebase overview, explain a project's architecture to newcomers, or asks "how does this codebase work". Also trigger when users say things like "document this repo for new devs", "write a getting started guide", or "help me understand this project".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
기존 코드의 일부를 감사하고 설계 결정 기록, 구현 관행, 누락 기능, 기술 선택의 네 관점에서 문제를 정리합니다. 계획부터 테스트, 수정, 재감사까지 진행합니다.
처음 접하는 코드의 구조와 처리 흐름, 개발 규칙을 조사해 프로젝트 참여 안내 자료와 CLAUDE.md를 만듭니다. 변경 작업별로 참고할 위치도 정리합니다.