This directory is the documentation portal for FeitozaUI.
Use it to understand the project vision, architecture, component platform decisions, design system rules, release planning, and future roadmap.
- Vision: project purpose, audience, and platform boundaries.
- Core Principles: required principles for components and platform work.
- Engineering Values: engineering habits expected in the project.
- Architecture: current architecture and intended platform structure.
- Decisions: ADR index and decision process.
- API Conventions: public component API rules.
- ADRs: architecture decision records.
- V1 Scope: frozen editorial catalog, API boundaries, and release validation.
- AI Docs Index: agent-specific entrypoint for repository rules and workflow.
- Project Context: repository surfaces, source-of-truth boundaries, and package scope.
- Official Sources: version-aware official references and compatibility notes.
- Next.js Guidelines: rules for the future showcase/documentation app.
- Component Workflow: required workflow for public component work.
- Review Checklist: practical review questions before concluding a task.
- Foundations: token categories and token strategy.
- Surface System: official surface hierarchy and visual weight model.
- Layout Principles: layout, spacing, density, and reading-order rules.
- Component Guidelines: how and when to create components.
- Component Checklist: readiness checklist for public components.
- Accessibility: accessibility standards.
- Developer Experience: API and usage quality expectations.
- Roadmap: maturity-based implementation plan.
- Future Roadmap: ideas outside the current scope.
- Releases: versioning and release strategy.
- Figma Make Reference: external visual and architectural reference kept for comparison, not as the official source of truth.
- Storybook: Storybook as documentation product.
- Testing Strategy: test scope and expectations.
- Performance: bundle and runtime performance direction.
- Maintenance: bug fixes, deprecations, and review process.
- Contributing: contribution workflow.
- Code Style: naming, organization, tests, and stories.
- FAQ: common project questions.