Kicking Off Apps
Take a rough app idea ("I want an app that…") to a new public GitHub repository cut from one of the user's template repositories, with signed-off requirements, UX flows, a researched design system, design decisions in the template's skills (no architecture docs), loose project permissions, and a dependency-ordered issue backlog for the template's shipping-issues. Orchestrates one child skill per stage — refining-requirements, designing-wireframes, ui-ux-designing, a design skill, bootstrapping-from-templates, configuring-project-permissions, designing-architecture, planning-tickets — and defer
Install
/plugin marketplace add tomada1114/tomada-claude-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tomada1114/tomada-claude-plugins --skill kicking-off-appsgit clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/kicking-off-apps ~/.claude/skills/kicking-off-appsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Kicking Off Apps The user plays the client: they describe an app loosely, and this skill runs the engagement — hearing, UX, visual design, repository, architecture, backlog — by calling one child skill per stage and carrying decisions between them in files. Without it each stage is done ad hoc, decisions made in conversation are lost at the session boundary, and the template's own conventions (its bootstrap, its lock format, its issue contract) get overwritten by generic defaults. This skill owns the order, the gates, the state file, and the handoff. It does not own any stage's content: each child skill does, and a template skill beats a global one on the same subject. ## Contract **Input:** the skill's argument — the app idea in the user's words, `resume`, `feature <request>`, or empty. Empty with no resumable run → ask for the idea in one open question. **`feature <request>`** runs a different, shorter engagement on an existing app's repository: scrutiny and hearing, optional wireframes and decisions, then a tracking issue with sub-issues. It writes no state and no documents — the requirements live in the issues. Follow [references/feature-mode.md](references/feature-mode.md) instead of everything below; only the question-round rules and the precedence of the repository's own skills carry over. **Output:** the new repository at `$(ghq root)/github.com/<owner>/<slug>` and the state directory described in [references/artifacts.md](references/artifacts.md), which also
Details
- Skill name
kicking-off-apps- Repository
- tomada1114/tomada-claude-plugins
- Path
tomada-kit/skills/kicking-off-apps/SKILL.md- Repo updated
- 12 November 2026
FAQ
What does the Kicking Off Apps skill do?
Take a rough app idea ("I want an app that…") to a new public GitHub repository cut from one of the user's template repositories, with signed-off requirements, UX flows, a researched design system, design decisions in the template's skills (no architecture docs), loose project permissions, and a dependency-ordered issue backlog for the template's shipping-issues. Orchestrates one child skill per stage — refining-requirements, designing-wireframes, ui-ux-designing, a design skill, bootstrapping-from-templates, configuring-project-permissions, designing-architecture, planning-tickets — and defer
How do I install the Kicking Off Apps skill?
Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Kicking Off Apps popular?
It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.
Related skills
Auditing Prompt Docs
5tomada1114/tomada-claude-plugins
Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m
Auditing Repositories
5tomada1114/tomada-claude-plugins
Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst
Authoring Goal Prompts
5tomada1114/tomada-claude-plugins
Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de
Refero Design
5tomada1114/tomada-claude-plugins
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this even when the user does not mention Refero and even when live Refero MCP tools are not configured. Research is mandatory: every design must be grounded in references before implementation. Provides research-first methodology, bundled craft knowledge, reference locks, decision ledg
Designing Wireframes
5tomada1114/tomada-claude-plugins
Create ASCII wireframes for every screen and window, user flow diagrams, and per-screen states (empty, loading, error) from a requirements document, for desktop (macOS windows, menu-bar popovers, settings), web (responsive app shells), and mobile. Writes into the requirements document in place, or into a separate file the caller names. Use when asked for a wireframe, screen layout, screen design, window layout, or user flow, to visualize screens before implementation, or as the UX stage of kicking-off-apps.
UI UX Designing
5tomada1114/tomada-claude-plugins
Produces one app-wide UX guidelines document (docs/design/ux-guidelines.md or a caller-named path) fixing navigation, platform conventions, empty/loading/error/offline/permission states, feedback, form validation, motion and reduced-motion, UI language and i18n, and accessibility targets as concrete values, settled through batched option-question rounds; also runs a measured WCAG contrast pass on a palette decided elsewhere. Use when settling app-wide behavior, deciding state handling, validation timing, motion policy, or accessibility targets, when a kickoff needs UX guidelines, or when a pal
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.