Customization

Your own rules

Put project rules next to the virastack/ folder, not inside it. ViraStack AI never reads, changes or deletes them:

.claude/rules/
├── virastack/        # managed by ViraStack AI
└── team.md           # yours
.cursor/rules/
├── virastack/        # managed by ViraStack AI
└── team.mdc          # yours

For other agents, write project instructions in AGENTS.md above or below the virastack-ai block.

Override a rule by name

The block tells agents to follow every ViraStack rule unless a project instruction names the rule it overrides. Name it in your own rule file or in AGENTS.md:

## Project rules

- Ignore the ViraStack `testing` rule: this project uses Playwright for end-to-end tests.

Editing a managed rule

• init notices the change from the manifest hash and asks before overwriting it.
• In CI, or with --yes, the file is skipped and keeps your version, so it no longer gets updates.
• remove keeps it unless you confirm.

Prefer your own rule file over editing a managed one: you keep your change and still get updates.

When to use --force

Use --force when you want to drop your edits to managed files and take the current version:

$ pnpm dlx @virastack/ai init --force

With remove, --force also deletes managed files you changed. In both cases your own rule files and text outside the AGENTS.md block stay.