donghyeon.kang/clean-architecture-frontend-template
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs: audit frontend platform capabilities

Browse Source
This commit is contained in:
donghyeon-ka
2026-07-26 02:09:06 +09:00
parent cb195f8773
commit 68342e25ce
13 changed files with 5934 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+19
View File
@@ -54,6 +54,25 @@ See `docs/architecture/overview.md`, `docs/architecture/layers.md`, and
visible starter routes do not depend on that fixture and continue to build
after it is removed.
### Platform capability review
The starter shell is implemented, but the repository review also records the
remaining work required before feature teams can use every declared contract
through one end-to-end application path:
- [platform capability review](docs/architecture/frontend-platform-capability-review.md)
- [ports, adapters, and feature boundaries](docs/architecture/frontend-ports-adapters-and-boundaries.md)
- [TypeScript, state ownership, and data flow](docs/architecture/typescript-state-and-data-flow.md)
- [routing, page templates, and reusable patterns](docs/architecture/routing-pages-and-patterns.md)
- [design-system platform](docs/styling/design-system-platform.md)
- [frontend platform testing strategy](docs/testing/frontend-platform-testing-strategy.md)
- [implementation roadmap](docs/architecture/frontend-platform-implementation-roadmap.md)
These documents distinguish repository defaults from opt-in adapters and
project-owned integrations. They are target designs and review findings; a
capability is not treated as implemented until its branch acceptance criteria
and executable gates pass.
## Verification
Common local checks: