erne-code
- Repo stars 36
- License MIT
- Author updated Live
- Author repo everything-react-native-expo
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: erne-code
description: ERNE — Implement features using the senior-developer agent You are executing the /erne-code comm…
category: engineering
runtime: no special runtime
---
# erne-code output preview
## PART A: Task fit
- Use case: ERNE — Implement features using the senior-developer agent You are executing the /erne-code command. Use the senior-developer agent to implement production-grade feature code. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Process / When to Use / Notes” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “ERNE — Implement features using the senior-developer agent You are executing the /erne-code command. Use the senior-developer agent to implement production-grade feature code. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Process / When to Use / Notes” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/erne-code`, `/erne-feature`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Process / When to Use / Notes”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: erne-code
description: ERNE — Implement features using the senior-developer agent You are executing the /erne-code comm…
category: engineering
source: JubaKitiashvili/everything-react-native-expo
---
# erne-code
## When to use
- ERNE — Implement features using the senior-developer agent You are executing the /erne-code command. Use the senior-de…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Process / When to Use / Notes” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "erne-code" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Process / When to Use / Notes
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}/erne-code — Feature Implementation
You are executing the /erne-code command. Use the senior-developer agent to implement production-grade feature code.
Process
- Understand the task — Read any existing architecture plan or feature description. If none exists, ask for scope and requirements.
- Analyze existing codebase — Read relevant files, understand current patterns, state management, and navigation structure
- Implement end-to-end — Using the senior-developer agent's process:
- Set up the file skeleton and type definitions
- Implement data layer first (API client, queries/mutations, stores)
- Build screens with all states handled (loading, error, empty, success)
- Wire navigation (route params, transitions, deep links)
- Handle edge cases (offline, token expiry, race conditions)
- Self-review — Check for re-renders, missing error handling, accessibility, type safety
- Deliver — Complete implementation with file paths, type definitions, and integration notes
When to Use
- Implementing a feature from an architect plan
- Building screens, hooks, API integration, and state management
- End-to-end feature work that touches multiple files
Notes
- Reference the active platform rules layer for conventions
- Follow the project's import ordering: react -> react-native -> expo -> external -> internal -> types
- If the task is a single isolated unit (one screen, one hook), consider
/erne-featureinstead
Decide Fit First
Design Intent
How To Use It
Boundaries And Review