ReddRadar
Agent skill
liftera-architecture
Liftera monorepo architecture patterns and best practices. Trigger: When making cross-app changes, adding new packages/apps, or deciding where code should live in the monorepo.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/liftera-architecture
Metadata
Additional technical details for this skill
- scope
-
[ "root" ] - author
- liftera
- version
- 1.0
- auto invoke
- General Liftera development questions
SKILL.md
Monorepo Boundaries (REQUIRED)
- ALWAYS keep application code inside
apps/*. - ALWAYS keep reusable code inside
packages/*. - NEVER import app code from another app (e.g.
apps/webimporting fromapps/mobile). Extract shared logic into a package.
Package Design (REQUIRED)
- ALWAYS design packages as platform-agnostic when possible.
- ALWAYS expose stable entrypoints from each package (avoid deep imports across packages).
- NEVER duplicate shared UI or utilities across apps; add/extend a package instead.
Cross-Platform UI Rules (REQUIRED)
- ALWAYS prefer shared UI in
packages/ui. - ALWAYS keep platform-specific implementations behind explicit entrypoints (e.g.
*.native.tsx,*.web.tsx) when needed. - NEVER assume DOM APIs exist in mobile code.
Dependency & Ownership Rules
- ALWAYS keep dependencies as low as possible in packages.
- ALWAYS add dependencies at the narrowest scope that needs them (package/app
package.json, not the root). - NEVER add a dependency to the root unless it is truly repo-wide tooling.
Repo Structure Quick Reference
apps/web: Next.js appapps/mobile: Expo apppackages/ui: shared UI (Gluestack UI + shared components)turbo.json: task orchestrationpnpm-workspace.yaml: workspace boundaries
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?