个人作者
Matheus Norjosa
Dev Python | IA | Automation | HTML | CSS | Data | Process | Projects
- Skills
- 53
- 仓库
- 1
- 职业覆盖
- 4
- 场景覆盖
- 2
- Stars
- ★ 0
Matheus Norjosa 的 Skills 53
writing-standards
Apply AS v2 technical-writing standards (clarity, brevity, active voice, Python/Django conventions). Use when writing a README, a docstring (PEP 257), a commit message, a PR description, an error message, or any technical doc.
verification-gate
Verify before claiming success. Use when about to say something works/is done, after implementing a feature, after a bugfix, or before pushing — run the proof command and confirm output first.
test-driven-development
Write the failing test before the implementation in AS v2 (pytest + Django/DRF). Use when implementing a feature or fixing a bug, before any production code is written.
subagent-development
Orquestra subagents no AS v2 — decompõe a tarefa em domínios independentes, paraleliza e revisa em 2 estágios. Use ao delegar exploração, implementação ou validação cross-arquivo para acelerar o trabalho e poupar o contexto principal.
security-scan
Automated security scanning for AS v2. Use before commits or when reviewing changes for vulnerabilities. Runs dependency audit (pip-audit, npm audit), secret detection (grep patterns), and code pattern scanning (SQL injection, XSS, eval, pickle, hardcoded secrets). Integrates with project hooks system.
resume-handoff
Resume work from a saved handoff document, validating its state against the current codebase before continuing. Use when resuming work from a saved handoff after a context clear or in a new session (path, session name, or GitHub issue).
receiving-code-review
Triage and respond to code review feedback for AS v2. Use when a PR has review comments, the user shares feedback, CI/linting flags issues, or after /review-staged or /review-enhanced runs.
ponytail
Modo "senior dev preguiçoso" contra over-engineering. Antes de escrever código, sobe uma escada e para no primeiro degrau que resolve: YAGNI → reusar o que já existe no codebase → stdlib → feature nativa da plataforma → dependência já instalada → uma linha → só então o mínimo que funciona. Deleção acima de adição, chato acima de esperto, o menor diff que funciona E que você entende. Use ao escrever código novo, adicionar feature, corrigir bug (causa-raiz, não sintoma) ou revisar um diff em busca de complexidade, abstrações ou dependências desnecessárias. Complementa (não substitui) as skills software-engineering e django-patterns. Snapshot fiel de DietrichGebert/ponytail (MIT).
plan-crosscheck
Adversarially cross-check an implementation plan against the REAL code before writing any of it. Fans out one verifier per plan-part that reads the code, confirms or refutes each claim with file:line, gives the concrete edit, and hunts for gaps — plus one skeptic that finds what the plan forgot. Use after drafting any non-trivial plan (multi-file, auth/RBAC/data-scope, migrations, many call-sites, contract/schema changes), BEFORE implementing.
performance-optimization
Profile and optimize AS v2 performance (Django backend + React frontend). Use when an endpoint is slow, a request fires N+1 queries, the bundle grows, or Core Web Vitals miss target.
memory-maintenance
Manter o dir de memórias (~/.claude/projects/.../memory/) e o índice MEMORY.md saudáveis — podar memória morta e corrigir o índice sem perder conhecimento. Use quando o dir inflar, o MEMORY.md encostar no cap de leitura (~24.4KB), ou você quiser limpar órfãs. Cobre a régua índice-vs-wikilink, a classificação A/B/C com grep -F, e o safety-grep obrigatório antes de deletar.
implement-plan
Implement an approved plan wave-by-wave with verification gates. Use when a plan path is given, when resuming after /clear, or when create-plan output is ready to build.
grill-with-docs
Entrevista implacável para afiar um plano ou design, registrando glossário e ADRs do Aprender Sistema durante a conversa.
graphify
Build/query a navigable knowledge graph of a codebase. Use when onboarding to an unfamiliar codebase, answering cross-module how-does-X-relate-to-Y, or tracing dependencies before a refactor.
git-worktrees
Work on multiple branches simultaneously without stashing or switching. Use when reviewing a PR while mid-feature, applying a hotfix without losing context, or comparing implementations side-by-side. Covers create/list/remove and AS v2 (Windows) conventions.
gate-calibration
Projetar um gate de CI que sobreviva — decidir se bloqueia, avisa ou usa ratchet; medir a precisão antes de escolher; limpar antes de trancar; e provar que ele não pode ser contornado. Use ao criar ou recalibrar qualquer check automático, especialmente sobre dívida preexistente.
frontend-ui-engineering
Build production-quality React UIs in AS v2 (React 19 + Antd v5 + Tailwind). Use when creating components, implementing pages, managing client state, or modifying any user-facing interface.
findings-crosscheck
Adversarially verify REPORTED findings against the real code before any of them becomes a task. Use when an audit, a security scan, another agent's relay, a "N fields are missing / X is broken" list, a bug report, or even your own claim from a past session asserts something is true about the system — triage the falsifiable claims, fan out one verifier per claim (file:line CONFIRMED/REFUTED/RECLASSIFIED), adversarially verify the consequential ones in BOTH directions, reproduce alarming numbers, and only let survivors become work.