Menu
Use when an agent needs extractor-recognized code-shape facts such as routes, htmx attributes, Alpine directives, SQL DDL/DML, or data-document structure.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use before changing existing indexed files with Miller edit, especially symbol rewrites, text replacements, renames, or refactors.
Use when starting a Miller task, choosing a Miller tool, or choosing a Miller search mode.
Use when tracing Miller bridge paths in supported providers: dotnet-web URL literals and fetch/axios client requests to ASP.NET signals, client requests to Next.js route handlers or Nuxt server routes, Next.js/Nuxt route references to file routes, Vue/React references to route definitions, or backend-http client requests to Express/FastAPI/Flask/Django/Spring/Go/gin/echo/Rails/NestJS/Laravel/Phoenix/axum/actix/Symfony/Ktor route facts.
Use when orienting on an unfamiliar code area with Miller, explaining a module, finding entry points, or gathering context before a change.
Use when assessing blast radius with Miller, choosing tests for a change, answering who uses a symbol, or planning a refactor.
Use when resuming Miller-backed work from a handoff packet or validating a packet before continuing in another harness, model, or session.
| name | miller-patterns-audit |
| description | Use when an agent needs extractor-recognized code-shape facts such as routes, htmx attributes, Alpine directives, SQL DDL/DML, or data-document structure. |
| user-invocable | true |
| arguments | <pattern family, path, language, or metadata filter> |
| allowed-tools | mcp__miller__patterns, mcp__miller__search, mcp__miller__inspect, mcp__miller__workspace |
Use patterns when the question is about known structural facts emitted by julie-extractors, not arbitrary AST
matching. Runtime list output is authoritative for the current catalog. Start by listing observed pattern IDs in
the selected workspace, then search the relevant ID with path, language, and metadata filters.
patterns(operation="list")
patterns(operation="list", language="razor")
List output includes Next: / JSON next_actions derived from observed IDs. Prefer those follow-up calls
before inventing a raw text grep.
patterns(operation="search", pattern_id="aspnet.minimal_api.route.v1", where="verb=GET")
patterns(operation="search", pattern_id="htmx.attribute.v1", where="name=hx-get", path="Views/**")
patterns(operation="search", pattern_id="alpine.directive.v1", where="directive=x-data", path="Views/**")
patterns(operation="search", pattern_id="sql.merge_statement.v1")
patterns(operation="summary", pattern_id="markdown.heading.v1", path="docs/**")
patterns(operation="summary", pattern_id="json.property.v1", language="json")
inspect(target="<path from pattern row>")
workspace_id.patterns is not a raw AST query engine.path, language, or where.search(mode="source") for arbitrary source text and search(mode="content") for docs/config prose.