multi

code

Implement features using the senior-developer agent

23 stars

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/code/SKILL.md --create-dirs "https://raw.githubusercontent.com/JubaKitiashvili/everything-react-native-expo/main/.claude/skills/code/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/code/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How code Compares

Feature / AgentcodeStandard Approach
Platform SupportmultiLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Implement features using the senior-developer agent

Which AI agents support this skill?

This skill is compatible with multi.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /code — Feature Implementation

You are executing the `/code` command. Use the **senior-developer** agent to implement production-grade feature code.

## Process

1. **Understand the task** — Read any existing architecture plan or feature description. If none exists, ask for scope and requirements.
2. **Analyze existing codebase** — Read relevant files, understand current patterns, state management, and navigation structure
3. **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)
4. **Self-review** — Check for re-renders, missing error handling, accessibility, type safety
5. **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 `/feature` instead