Imported from alphadoiy/L2 (
AGENTS.md). Install upstream withnpx skills add alphadoiy/L2. Copyright stays with the author.
Agent Instructions
Waza Skill Priority
For this project, prefer the installed Waza skills for development and design work when a request matches their purpose. Read the matching SKILL.md before acting and follow its workflow instead of improvising a generic process.
Use this routing first:
| Skill | Prefer When |
|---|---|
think |
Planning a new feature, architecture, feasibility, product judgment, or "how should this be designed?" |
design |
UI, frontend, page, component, typography, visual polish, layout problems, or screenshots that look wrong. |
check |
Code review, pre-merge validation, follow-up optimization, release readiness, push or issue follow-through. |
hunt |
Bugs, crashes, regressions, failing tests, unexpected behavior, or anything that used to work. |
write |
Drafting, rewriting, proofreading, docs, launch copy, or removing stiff AI-style phrasing. |
learn |
Deep dives into unfamiliar domains or turning a set of sources into a coherent article or brief. |
read |
Reading URLs, PDFs, or external documents before summarizing, quoting, citing, or feeding another task. |
health |
Agent instruction drift, hooks or config misfires, verifier issues, or broad project health audits. |
If more than one Waza skill seems applicable, read each candidate skill's "Not for" or boundary guidance and choose the narrowest match. If it is still ambiguous, ask the user which workflow should take precedence.
Development Standard
Use Development Guidelines as the project-wide workflow for non-trivial development work. Its scope-plan-implement-verify-review-deliver sequence is the default unless a task is small enough to complete and verify directly.
Treat these requirements as hard rules:
- Keep the evaluated agent core original; use external projects for research, not copied implementation.
- Never commit or expose API keys, secrets, or credentials in code, logs, screenshots, fixtures, or deliverables.
- Define acceptance criteria and verification steps before implementing a non-trivial change.
- Keep architecture, module, runbook, and interaction docs synchronized with behavior changes.
- Before committing or handing off code, check for circular dependencies, broken one-way data flow, duplicated sources of truth, and redundant or unnecessarily complex logic.
- Run
npm run check, review the resulting diff and repository state, and complete the applicable manual or end-to-end checks before handoff.