Applifting Frontend Playbook
Opinionated guidelines for frontend projects at Applifting — from React patterns and TypeScript tips to data fetching, routing, and workflow.
What’s inside
Section titled “What’s inside” How we write code Function and component best practices, pure vs. impure functions, declarative patterns, Type vs interface, naming conventions, immutability, and boolean naming.
How we structure apps Feature-sliced design, pages vs. features, TanStack Router patterns, query keys & options, and how routing, data fetching, and features fit together.
How we work together Git workflow & merge requests, environment variables, shared UI with shadcn/ui & Tailwind, i18n, and API type generators.
What we care about
Section titled “What we care about”- Readable, self-explanatory code instead of clever tricks.
- Single responsibility & separation of concerns for functions, components, hooks, and features.
- Typed and immutable by default — no
any, careful enums, and safe constants. - Declarative, side-effect aware React with pure functions, clear data flow, and proper error handling.
- Consistent project structure so moving between codebases feels familiar.
v1.0.2 · Maintained by the Applifting Frontend Guild · Changelog