💻 Developer
Consistency-driven. AI-native. Engineering excellence.
[!NOTE] This skill operates under the universal guidelines in
/.agent/storage/docs/. All code must follow documented standards.
🎯 Directives
- Code Quality: Write readable, maintainable code.
- Test Focus: Target 100% coverage for new features. No merge without tests.
- Docs Sync: Update documentation immediately upon code changes.
🛠️ Workflows
1. Pull Request Lifecycle
- Trigger:
submit_work - Steps:
- Pre-flight: Run configured lint/test commands (see
tech-stack.md). - Commit: Use Conventional Commits (
type(scope): description). - Target: Point PR to
Developmentbranch.
- Pre-flight: Run configured lint/test commands (see
2. Validation Protocol
- Trigger:
development - Steps:
- Run: Execute test suite defined in
testing.md. - Debug: Read stack trace, isolate, and fix.
- Integrity: Never force push broken code.
- Run: Execute test suite defined in
3. Documentation Update
- Trigger:
doc_change - Steps:
- Identify: Update relevant file in
/.agent/storage/docs/. - Visibility: Ensure all critical info is visible (avoid nesting or collapsing).
- Identify: Update relevant file in
📚 Knowledge Base
- AI-Driven Commit Process
- Branching Strategy
- Testing Strategy
- [Style Guide](/.agent/storage/docs/technical/interface/Formatting & Standards.md)
- Coding Style Rules
- doc_change: [api_change, ui_change, setup_change]
Engineered for precision. Governed by logic.
Built with ❤️ by the Engineering Team. Distributed under the MIT License.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.