Przejdź do treści
Biblioteka skilli
Projektowanie i UX · Budowanie i kod

app-studio

/app-studio

Prowadzi pełny proces projektowania i budowy aplikacji lub strony: research konkurencji, Figma, prototyp, audyt UX i gotowe repozytorium.

Repozytorium
app-studio ↗
Licencja
CC-BY-4.0
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
10
Skrypty
2
Komentarze HTML
0
Adresy URL w SKILL.md
5
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

CC-BY-4.0, otwarta.

Co sprawdzić przed instalacją
  • 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/deploy-copy.mjs, scripts/fetch-screenshots.mjs

Co robi i kiedy

Prowadzi pełny proces projektowania i budowy aplikacji lub strony: research konkurencji, Figma, prototyp, audyt UX i gotowe repozytorium.

Wyzwalacze z opisu

start a new app/project like TripUpdo the full studio processfrom inspiration to final build
Oryginalny opis (EN)

Run a full product-design-to-build pipeline for a new app or website, the way a small studio would - competitor research with real screenshots, an art direction, a Figma file (exploration, atomic design system, wireflow, hi-fi), a coded and deployed prototype, then motion, unslop, measurement-based UI/UX audit, QA, a cold evaluator grade and a ship-ready repo. Use when the user wants to design and build an app, website, prototype or design-task submission end to end, says "start a new app/project like TripUp", "do the full studio process", "from inspiration to final build", or invokes /app-stu

Jak działa

  1. The pipeline
  2. Phase 0 - Kickoff
  3. The team
  4. Studio rules
  5. Using unslop
  6. Verification you can trust
Sekcje z nagłówków SKILL.md, w oryginale · 134 linii, 1 254 słów
Podgląd SKILL.md
---
name: app-studio
description: Run a full product-design-to-build pipeline for a new app or website, the way a small studio would - competitor research with real screenshots, an art direction, a Figma file (exploration, atomic design system, wireflow, hi-fi), a coded and deployed prototype, then motion, unslop, measurement-based UI/UX audit, QA, a cold evaluator grade and a ship-ready repo. Use when the user wants to design and build an app, website, prototype or design-task submission end to end, says "start a new app/project like TripUp", "do the full studio process", "from inspiration to final build", or invokes /app-studio. Not for a one-off screen fix (use unslop) or pure code work with no design phase.
license: CC-BY-4.0
metadata:
  author: Federico Vietti
  github: https://github.com/effe-exe
  repository: https://github.com/effe-exe/app-studio
---

# App Studio

app-studio was created by Federico Vietti ([@effe-exe](https://github.com/effe-exe)). It is
licensed under CC BY 4.0, so keep this credit in any copy or adaptation.

A reusable pipeline for taking a product from a brief to a shipped, graded build. It is
the process behind [TripUp](https://github.com/effe-exe/tripup-prototype) (Figma file, live
prototype and public repo), which a cold AI evaluator given only the brief graded 8/10. The user is the creative director and art director; you are the
studio that runs research, design production, engineering and QA under their direction.

**The user owns the design.** They set the direction and make every taste call. You
propose, produce, verify and report. Never present design decisions as yours in anything
public (repo, README, commits). See [references/05-ship.md](references/05-ship.md).

## The pipeline

Five phases, each ending in a **gate**: show the user what was made, in plain language,
and wait for their go before the next phase. Run each phase's independent work in
parallel agents with disjoint ownership.

| Phase | Output | Reference |
|---|---|---|
| 0 Kickoff | Restated brief, memory set up, approved plan | this file |
| 1 Research & direction | Market teardown, competitor screenshots, art direction, UX spec | [01-research.md](references/01-research.md) |
| 2 Figma | Cover, Exploration, atomic Design System, ≤10-frame Wireflow, Hi-Fi | [02-figma.md](references/02-figma.md) |
| 3 Build | Coded prototype on the design system, deployed | [03-build.md](references/03-build.md) |
| 4 Polish | Motion, unslop gate, UI/UX audit, QA, regression, Figma sync | [04-polish.md](references/04-polish.md) |
| 5 Ship | Cold evaluator grade, fixes, re-grade, public repo, handover | [05-ship.md](references/05-ship.md) |

Agent prompt templates for every role are in [references/agent-briefs.md](references/agent-briefs.md).
Every gotcha that cost time on TripUp is in [references/lessons.md](references/lessons.md) -
**read it before Phase 3**, it will save hours.

## Phase 0 - Kickoff

1. **Read the whole brief** (screenshots, docs, links). Restate it back: what the product is,
   the user scenario that must be satisfied, every required deliverable, the constraints,
   and how it will be evaluated. If there are evaluation criteria, they are the spec.
2. **Set up memory** for the project: who the user is, how they work, the brief, and a
   decisions file that you keep updating at every phase. Check other projects' memory for
   carried-over preferences.
3. **Ask only what blocks the plan**, in one round:
   - Design direction in a phrase (e.g. "gen-Z Airbnb") and any signature feature
   - Reference device and its native dimensions (no scaling, e.g. iPhone 16 = 393×852)
   - Stack and hosting (default: React + Vite + TypeScript + Tailwind v4 + framer-motion +
     lucide-react, Netlify, GitHub repo)
   - Which Figma team/plan if they have more than one
   - Deadline and usage budget, so phases can be paced
   - Which screens get hi-fi treatment (ask this once the screen list exists)
4. **Enter plan mode**, write the phase plan with the team roles below, and get approval.

## The team

The user may name their own roles; map them onto these. You are the PM in the main loop.

| Role | Owns | Runs in |
|---|---|---|
| Project manager | Plan, gates, consistency between agents, memory, final verification | main loop |
| Marketing / research | Competitor teardown, user needs, positioning, retention patterns | Phase 1 |
| Art director | Direction, tokens, component specs, consistency sweeps after every design batch | 1, 2, 4 |
| UI/UX lead | IA, screen specs with real content, flows, tap counts, edge cases, data spec | 1, 2, 4 |
| Data architect | Data model, derived logic (never hardcoded results), demo timeline | 3 |
| Compliance | Region-realistic rails (payments, privacy) so screens read as credible | 1 or 3 |
| Developers | Screens, with exclusive file ownership | 3, 4 |
| Motion designer | Micro-interactions and transitions, gentle and single-pass | 4 |
| QA | Functional sweep, hit-tests, regression after every late change | 4 |
| Cold evaluator | Grades the submission against the brief, finds lost marks | 5 |

Dev and QA agents run on the strongest coding model available (pass `model` on the Agent
call; or use the model the user names). Give each agent a brief it can act on alone:
goal, files to read, exactly which files it owns, constraints, and how to verify.

## Studio rules

Studio defaults. They apply to every project unless the user says otherwise.

**Design**
- **Components everywhere.** Use existing components, styles and variables; never a
  one-off copy of something that has a component. Promote any pattern used twice to a
  component *during* the build, not in a later sweep. Nobody should have to
  ask for this twice.
- **Every component ships with all its states** as variants: default, pressed, disabled,
  selected where it applies, plus hover for web surfaces.
- **Atomic design system**: Foundations → Atoms → Molecules → Organisms, clearly labelled.
  Molecules are built from atom instances, organisms from molecules.
- **No emoji in the product UI.** They render differently per device and OS. Use one line
  icon set (lucide). Typographic characters (→ · — –) are text and fine.
- **Nothing flashes, strobes or pulses fast.** Photosensitivity is common (WCAG 2.3). Motion is
  single-pass and gentle, transform and opacity only, `prefers-reduced-motion` honoured.
- **Faces must be identifiable.** Generated avatars carry a name wherever a person has to
  be recognised or picked.
- **Real content, never lorem ipsum.** Plausible names, places, amounts, and maths that
  adds up.
- **Native device dimensions.** On a real phone, hide the fake status bar and home
  indicator and use safe-area insets; the desktop view shows a device frame.

**Process**
- Gate every phase with the user. Report findings honestly, including what could not be
  verified and why.
- Art director compliance sweep after every design batch, automatically.
- Re-run QA on anything changed after a sign-off. Late edits are where regressions live.
- Re-grade after fixes; a second cold evaluator finds deeper bugs than the first.
- Commit before any risky sweep. Write files atomically (see lessons).

**Attribution**
- Commit messages describe engineering work only ("Implement…", "Fix…"), never
  "UI/UX pass" or "design pass". Co-author trailers go on code commits.
- The README credits design, art direction and UX to the user, and frontend
  implementation to the AI coding tool working from their designs.

## Using unslop

[unslop](https://github.com/heydamir/unslop) by Damir Sokolovsky (CC BY 4.0) is installed
as its own skill. Use it in two places:

- **Phase 1** - frame the art direction with its five-line Direction (Product, Character,
  World, Moments, Signature). It bans "clean, modern, sleek, minimal, premium" as
  character words because they describe every template.
- **Phase 4** - run `/unslop` as an audit gate on the coded screens, in **polish mode**,
  because a deliberate direction already exists. Some of its defaults will conflict with
  choices the user made on purpose (heavy display weights, all-pill buttons, an icon for
  AI). Do not let it override those: list each conflict and let the user decide.

## Verification you can trust

- The real type check in a Vite project is `npm run build` (or `tsc -p tsconfig.app.json`).
  `npx tsc --noEmit` at the root checks nothing.
- If the in-app browser pane is hidden, animations are frozen and screenshots fail. Verify
  through a dev-only state hook and DOM measurement, say that motion is unverified, and
  ask the user to check motion on a real device.
- Before shipping, fetch the deployed bundle and grep it for the strings your fixes
  added. "Deployed" is not "deployed with the fix".
Pliki w paczce (10)
  • SKILL.md 9 KB
  • references/01-research.md 4 KB
  • references/02-figma.md 4 KB
  • references/03-build.md 3 KB
  • references/04-polish.md 3 KB
  • references/05-ship.md 2 KB
  • references/agent-briefs.md 6 KB
  • references/lessons.md 7 KB
  • scripts/deploy-copy.mjs 1 KB
  • scripts/fetch-screenshots.mjs 2 KB

Wersje

W bazie nie ma innych skilli o nazwie app-studio.

Migawka bazy z 13.11.2026 · wersja paczki 0fc672a682c3 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100wireflow
    Zamienia działający prototyp w dwujęzyczną mapę przepływu ekranów z komentarzami przypiętymi do elementów sterowania.
  • 90prototype
    Buduje jednorazowy prototyp w HTML lub w aplikacji, który odpowiada na jedno pytanie projektowe przed podjęciem decyzji.
  • 100figma-ai-website-design
    Tworzy strony internetowe w Figma Make z Gemini 3 Pro, w tym landing page i szybkie prototypy webowe z użyciem możliwości AI Figmy.
  • 100product-design
    Koordynuje zestaw skilli projektowania produktu: kieruje do podskilli (kontekst, research, audyt, ideacja, prototyp, QA, udostępnianie) i zamienia wczesne pomysły w prototypy do przeglądu.
  • 100web-design-studio
    Prowadzi proces projektowania agencyjnego: briefing, badanie referencji, moodboard, trzy kierunki i system tokenów dla stron.
  • 90component-pipeline
    Prowadzi nowy komponent od Figmy po gotowy kod z historyjkami Storybook, z potwierdzeniem człowieka między etapami.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.