Less unnecessary code.
Reuse what fits. Add only what the task needs. Preserve existing behavior and user work; ask before destructive changes.
A rulebook for focused changes, safer decisions, and stopping a two-file change from becoming a six-layer architecture.
Practical rules for AI coding agents
No framework required. No custom index. No “enterprise-ready” abstraction for a button.
Reuse what fits. Add only what the task needs. Preserve existing behavior and user work; ask before destructive changes.
Start with the context you provided. Follow relevant files and dependencies, then expand the search only when the task needs it.
Follow the product, brand, and existing design system. Use Impeccable for UI/UX work, then critique the result instead of repeating a template.
Require local checks for new or changed API behavior. Report what actually passed, what could not be tested, and what remains uncertain.
Global rules, eight task-specific guides, and the bundled Impeccable UI/UX skill. Read what the task needs; keep the global rules in scope.
Using Claude Code, Gemini CLI, or another coding agent?
You may need to rename AGENTS.md to the instruction filename
expected by your tool (for example, CLAUDE.md or
GEMINI.md).
as-kiss.zip
AGENTS.md
README.md
agent-guides/
├── engineering.md
├── backend.md
├── frontend.md
├── uiux-ds.md
├── testing.md
├── code-style.md
├── payments.md
└── access.md
.agents/skills/impeccable/
├── SKILL.md
├── agents/
├── reference/
└── scripts/
Inspect the supplied context first, preserve user work, and verify the changed behavior. Global rules stay in scope even when only a few guide sections are needed.
Read the bundle overview · Read the global rules
This bundle has env_file_read: on. It permits task-relevant reading of project-local environment files. It does not allow secret exposure or environment-file edits. Review access.md.
Keep the folder structure intact and review the access settings. Merge with existing project instructions before asking your agent to use them.
Download as-kiss.zip, containing the files listed above.
You should see AGENTS.md, README.md, agent-guides/, and the hidden .agents/ folder.
Place the rules where they should apply: at the shared root for a monorepo, or the app root for a single app. Keep agent-guides/ and .agents/ alongside the instruction file. Merge existing instructions and skills rather than overwriting them; use the bundled README as reference.
Example layouts below. Highlighted entries are the files and folders to add or merge.
my-app/
├── AGENTS.md
├── agent-guides/
├── .agents/
│ └── skills/
│ └── impeccable/
├── src/
├── package.json
└── README.md
my-workspace/
├── AGENTS.md
├── agent-guides/
├── .agents/
│ └── skills/
│ └── impeccable/
├── apps/
│ ├── web/
│ └── api/
└── README.md
Only one app needs the rules? Put the same three highlighted entries inside that app’s root instead. Keep your existing project README; the bundle README is installation reference.
Some agents expect names like CLAUDE.md or GEMINI.md. Keep agent-guides/ and .agents/ beside it.
Have your agent read the global rules first, then the relevant guide sections and required references. UI/UX work uses the bundled Impeccable skill; its launcher may download its runtime on first use.
Give it rules for what to change, when to ask, and how to show the work was verified.