erne plan

Design Community

Skill notes

Process

Understand the requirement — Ask clarifying questions if the feature description is vague Analyze existing codebase — Read relevant files, understand current navigation structure, state management, and API patterns Design the architecture — Using the architect agent's process: Decompose into components and screens Plan Expo Router file structure

Architecture Output

Review with user — Present the plan and ask for approval before implementation

Notes

Reference the active platform rules layer (rules/expo/patterns.md or rules/bare-rn/patterns.md) for conventions Consider whether this is Expo managed, bare RN, or has native modules Include test strategy in the plan

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@JubaKitiashvili · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview erne-plan.preview
# Architecture Output

```

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.