How do I install the App Dev skill?

Run npx skillmds@latest add wwf971/app-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is App Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with App Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is App Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published App Dev?

wwf971 (@wwf971) published this skill. Their other Agent Skills are listed on their SkillMD profile.

App Dev by wwf971 — Agent Skill

Name: App Dev
Author: wwf971

App Dev

Follow app development guidance for frontend, backend, UI interactions, naming, IDs, timestamps, deployment, and project documentation. Use when designing or editing application code, APIs, React or MobX UI, in-place editing, selectors, CloudFront prefix deployment, or implementation design documents.

wwf971 Updated Sep 22, 2026

File contents

App Development

For application development tasks, refer to the reference files that match the current task before designing or editing code.

Core References

For naming variables, fields, functions, components, stores, API data, or operational state, refer to references/naming.md.

For frontend code, especially React, MobX, component structure, package imports, icons, editable UI, or visual stability, refer to references/frontend-design.md.

For backend APIs, HTTP response format, request handling, or backend data shape, refer to references/backend-design.md.

For timestamps, timezone fields, time serialization, database time columns, or time-based display, refer to references/time-format.md.

For IDs, database primary keys, random IDs, or time-based IDs, refer to references/id-format.md.

UI Feature References

For in-place editing, inline renaming, contenteditable behavior, submit or cancel behavior, locked edit state, or IME-sensitive editing, refer to references/renaming.md.

For selector UI, choosing one or more resources, searchable dropdowns, selected tags, cached search results, selector state, or selector-backed MobX stores, refer to references/selector.md.

Deployment Reference

For apps deployed behind CloudFront, reverse proxy, URL prefix, Vite base path, prefixed API URL, forwarded auth, or WebSocket through proxy, refer to references/deploy-cloudfront.md.

When Writing Documents

For explaining an overall implementation plan, such as architecture choices or semantic model of core concepts, refer to references/doc-design.md.

For summarizing debug experience, refer to references/doc-tech-guide.md.

Working Rules

For project-specific choices, prefer the referenced guidance over generic defaults.

For tasks where multiple references apply, read all relevant files before making changes.

For old relative paths inside reference files, resolve them within the references/ folder.

---name: app-devdescription: Follow app development guidance for frontend, backend, UI interactions, naming, IDs, timestamps, deployment, and project documentation. Use when designing or editing application code, APIs, React or MobX UI, in-place editing, selectors, CloudFront prefix deployment, or implementation design documents.---# App DevelopmentFor application development tasks, refer to the reference files that match the current task before designing or editing code.## Core ReferencesFor naming variables, fields, functions, components, stores, API data, or operational state, refer to `references/naming.md`.For frontend code, especially React, MobX, component structure, package imports, icons, editable UI, or visual stability, refer to `references/frontend-design.md`.For backend APIs, HTTP response format, request handling, or backend data shape, refer to `references/backend-design.md`.For timestamps, timezone fields, time serialization, database time columns, or time-based display, refer to `references/time-format.md`.For IDs, database primary keys, random IDs, or time-based IDs, refer to `references/id-format.md`.## UI Feature ReferencesFor in-place editing, inline renaming, contenteditable behavior, submit or cancel behavior, locked edit state, or IME-sensitive editing, refer to `references/renaming.md`.For selector UI, choosing one or more resources, searchable dropdowns, selected tags, cached search results, selector state, or selector-backed MobX stores, refer to `references/selector.md`.## Deployment ReferenceFor apps deployed behind CloudFront, reverse proxy, URL prefix, Vite base path, prefixed API URL, forwarded auth, or WebSocket through proxy, refer to `references/deploy-cloudfront.md`.## When Writing DocumentsFor explaining an overall implementation plan, such as architecture choices or semantic model of core concepts, refer to `references/doc-design.md`.For summarizing debug experience, refer to `references/doc-tech-guide.md`.## Working RulesFor project-specific choices, prefer the referenced guidance over generic defaults.For tasks where multiple references apply, read all relevant files before making changes.For old relative paths inside reference files, resolve them within the `references/` folder.

Frequently asked questions