ARCHITECTURE.md`, `PITFALLS.md` |
**Capabilities:**
- Web search for current ecosystem information
- Context7 MCP integration for library documentation
- Writes research documents directly to disk (reduces orchestrator context load)
---
### gsd-phase-researcher
**Role:** Researches
Write unit tests for new functionality focusing on behaivor and not
implementation.
4. Document public APIs and complex logic.
5. Suggest changes to the `docs/` folder when appropriate
6. Follow
FLUX Best Practices
**Version 1.0.0**
Black Forest Labs
January 2026
> **Note:**
> This document is for AI agents and LLMs to follow when working with
> FLUX image generation prompting and workflows
React Best Practices
**Version 1.0.0**
Vercel Engineering
January 2026
> **Note:**
> This document is mainly for agents and LLMs to follow when maintaining,
> generating, or refactoring React and Next.js codebases. Humans
import generated OpenAPI types/client code from `ui/desktop/src/api`
## Code Quality
- Comments: Write self-documenting code - prefer clear names over comments
- Comments: Never add comments that restate what code does
- Comments: Only
Documentation Style Guide
## Brand Guidelines
**IMPORTANT**: The product name "goose" should ALWAYS be written in lowercase "g" in all documentation, blog posts, and any content within this documentation directory.
- ✅ Correct
point:** Use [`analyze()`](analysis-api/src/org/jetbrains/kotlin/analysis/api/analyze.kt) to start an analysis session. See [Analysis API documentation](https://kotl.in/analysis-api) for a usage guide.
## Architecture
- **Platform** — Provides declarations, project structure, and modification
list`, and `claude plugin validate .`.
## Writing style
Use Plain Language in code comments, prompts, documentation, descriptions, validation messages, and progress reports.
- Lead with the main point.
- Use common words
React Best Practices
**Version 1.0.0**
Vercel Engineering
January 2026
> **Note:**
> This document is mainly for agents and LLMs to follow when maintaining,
> generating, or refactoring React and Next.js codebases. Humans
review discussion.
During code review, check the proposed changes against all applicable code, test,
documentation, and architectural conventions in this `AGENTS.md`. Report
meaningful violations introduced by the changes
after locating or installing the repository. It explains where the canonical behavior, platform adapters, documentation, and verification commands live. It does not replace the skill rules in `skills/i-have-adhd/SKILL.md`.
## Start here
protocol limits, usage sources, defaults, estimation, and settlement details in code comments or technical documentation. Descriptions must be short, equivalent across languages, and free of numeric prices and trailing punctuation
common case.
Database contracts belong to `packages/data-schemas`. Keep Mongoose types (`FilterQuery`,
`Types.ObjectId`, `Document`) out of exported signatures in `packages/api`, `packages/data-provider`
and `client`, because they make the storage engine part
security`** skills.
## Development Services
Local dependencies are managed by `devservices` (config: `devservices/config.yml`).
📖 Full devservices documentation: https://develop.sentry.dev/development-infrastructure/devservices.md
## AI Assistant Quick Decision Trees
### "User wants to add an API endpoint
install`, `pnpm run build`).
## Code Style
- Do not use emojis in code, output, or documentation. Unicode symbols (✓, ✗, →, ⚠) are acceptable.
- In documentation and markdown, never use double hyphens (`--`) as a dash
opening a pull request instead of pushing `master` directly. Small, low-risk changes and documentation-only updates can use a lighter workflow when Can prefers it.
Immediately before opening
bypass only defers the same failure to CI.
## Testing (Jest)
> Tests are documentation first. Describe blocks = table of contents; `it()` = plain English; assertions = response shape. Write failing tests before implementation
React Composition Patterns
**Version 1.0.0**
Engineering
January 2026
> **Note:**
> This document is mainly for agents and LLMs to follow when maintaining,
> generating, or refactoring React codebases using composition. Humans