-
Notifications
You must be signed in to change notification settings - Fork 0
how to contribute
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
Start by matching the product vocabulary in CONTEXT.md, then follow the package scripts in package.json. Most changes touch either the React controller/view layer in frontend/src, the Tauri command bridge in src-tauri/src, or the Rust core in crates/qa-scribe-core/src.
- Identify whether the change is a feature, core data-model change, provider change, UI change, release-tooling change, or test-only change.
- Read the relevant feature page under Features and subsystem page under Systems.
- For data-shape changes, update Rust domain types, Specta registration in
src-tauri/src/specta_bindings.rs, generatedfrontend/src/bindings.ts, frontend wrapper code, and tests together.
A finished change has updated code, updated bindings when needed, tests covering the behavior, and the relevant verification command passing. Use Testing for command selection and Tooling for packaging and release checks.
- QA Scribe
- Download overview video (MP4)
- Architecture
- Getting started
- Glossary
- By the numbers
- Lore
- Fun facts
- Video overview
- How to contribute
- Development workflow
- Testing
- Debugging
- Patterns and conventions
- Tooling
- Applications
- Desktop app
- Smoke harness
- Systems
- Rust core
- Tauri command bridge
- Frontend shell
- Generation jobs
- Provider detection
- Release tooling
- Features
- Session capture
- Rich record editing
- Managed attachments
- AI-assisted Testware
- Settings and provider setup
- Crates
- qa-scribe-core
- qa-scribe-app
- Primitives
- Session
- Entry
- Finding
- Draft
- Evidence
- API
- Tauri commands
- Deployment
- Security
- Background
- Architecture decisions
- Migration context
- Cleanup opportunities
- TODOs and FIXMEs
- Complexity hotspots
- Reference
- Configuration
- Data models
- Dependencies