configuration, or recommended usage changes.
## Go design conventions
Follow Effective Go and the Go CodeReview Comments, while preserving
established APIs when compatibility requires it.
- Use `gofmt` and `goimports
verification
succeeds against the public release.
---
## Compiler and Test Checks (CRITICAL)
**After any substantive code changes, use the one authoritative quality entry
point:**
```bash
dsr quality --tool pi_agent_rust
open
`SKILL.md` format, cross-provider). Shared skills, convention rules, `/create-pr`,
`/create-changeset`, `/create-branch`, `/create-issue`, the `code-reviewer` subagent, and the
`house` output style come from the `agents` plugin
([stijnvanhulle/agents](https://github.com
have to review; only per-community skills, which
describe that specific codebase, are written into the repo.
| Host | Skills | Slash commands | Sub-agents | Enforcement hooks |
| --- | --- | --- | --- | --- |
| Claude Code | `~/.claude/skills/` | `~/.claude/commands/` | `~/.claude/agents
pass all linting process
- Add changelog entry to `CHANGELOG.md`, follow our existing format
## Codereview
- Code should use as much immutable (via `Object.freeze()`) as possible, DO NOT trust `readonly
code indexes it).
- **⚠️ Third-party MCP servers launch isolated**: any stdio MCP server whose code we don't own runs via `uvx`/`npx` with pinned versions, never from the shared
diagnostics);
review and redact any diagnostic excerpt before sharing it. MemoraX receives
only documented query/add/writeback payloads; local trace provenance and
transcript paths stay local.
- Keep the shared `memorax-code` Skill
commit.
- `.agents/skills/happier-review` is the only general Happier review/QA orchestrator. The archived `review-protocol` and `code-reviewer` skills must not be invoked.
- `.agents/skills/happier-pr-steward` for user-requested pull-request stewardship; it composes
TypeScript configs
yarn update-readme # Regenerate API docs
```
CI uses `suggestion-bot` to post codereview suggestions for format,
constraints, align-deps, and readme issues.
## Platform-Specific Notes
- **Test apps
force-add files into them (`git add -f`).
- **No PR review artifacts.** Code-review notes (`pr-*-review*.md`) belong in the PR discussion thread, not as committed files.
- **The `downloads
agents working on the Scion Web Frontend.
## Design Documents
Before making changes, review the relevant design documentation:
- **[Web Frontend Design](../.design/hosted/web-frontend-design.md)** - Architecture, technology stack, component patterns
## Architecture Overview
works
- Check compatibility with Foundry Local
### Review Process
- Educational content changes are reviewed for accuracy and clarity
- Code samples are tested for functionality
- Translation updates are handled automatically by GitHub
works
- Check compatibility with Foundry Local
### Review Process
- Educational content changes are reviewed for accuracy and clarity
- Code samples are tested for functionality
- Translation updates are handled automatically by GitHub
nieuwe branch aan vanuit `main`
2. **Breng je wijzigingen aan** volgens de richtlijnen voor code-stijl
3. **Test grondig** met behulp van de testinstructies hierboven
4. **Commit met duidelijke berichten