rainze-code-writer
Build and update Rainze code using the PRD, tech stack, and module sub-PRDs. Use this when writing Python/Rust for Rainze, aligning with the architecture, method signatures, class/layout definitions, and coding standards under .github/references.
When & Why to Use This Skill
The rainze-code-writer is a specialized development agent designed to automate the implementation and maintenance of the Rainze codebase. It translates PRDs and technical specifications into high-quality Python and Rust code while ensuring strict adherence to project-specific architecture, method signatures, and coding standards like PEP 8 and Rust style guides. It excels at managing complex cross-language boundaries and enforcing centralized context management.
Use Cases
- Translating module-specific PRDs and technical requirements into functional Python or Rust implementations.
- Developing high-performance system components in Rust with PyO3 bindings for seamless Python orchestration.
- Refactoring existing code to align with updated class layouts, method signatures, and shared core contracts.
- Enforcing architectural consistency by routing interactions through the UnifiedContextManager and reusing shared types.
- Automating code reviews and updates to ensure compliance with project-specific coding standards and documentation.
| name | rainze-code-writer |
|---|---|
| description | Build and update Rainze code using the PRD, tech stack, and module sub-PRDs. Use this when writing Python/Rust for Rainze, aligning with the architecture, method signatures, class/layout definitions, and coding standards under .github/references. |
Rainze Code Writer
Specialized agent for implementing Rainze features across Python and Rust. Keep replies focused on execution; avoid generic tips.
Use when
- Implementing or modifying Rainze features, modules, or bindings.
- Translating PRD requirements into code using module method signatures/class layouts.
- Enforcing Rainze tech stack choices and coding standards.
Quick start
- Read
references/docs-index.mdto pick the right PRD/tech/module docs. - Open the relevant module sub-PRD for method signatures and class/struct layouts before coding.
- Follow the workflow checklist in
references/workflow.md.
Core rules
- Route interactions through
UnifiedContextManager; do not bypass with direct module calls unless the contract allows. - Reuse shared types from
core.contracts(scene, emotion, interaction, rust bridge, tracer) instead of redefining. - Respect Python/Rust boundaries: heavy compute and system monitoring stay in Rust (PyO3 bindings), orchestration/UI/AI wiring stay in Python.
- Keep configs in sync with documented schemas; update defaults and examples when changing behavior.
- Apply coding standards: Python PEP 8 (
.github/references/python/pep8.md), Rust style (.github/references/rust/style.md).
References
- Module and doc map:
skills/rainze-code-writer/references/docs-index.md - Workflow and checklists:
skills/rainze-code-writer/references/workflow.md - Coding standards (source):
.github/references/python/pep8.md,.github/references/rust/style.md