forma
/forma
Koordynuje specjalistów od designu i wybiera umiejętność do interfejsu, kolorów, marki lub audytu, składając wspólny brief.
- Autor
- figueirego ↗
- Repozytorium
- forma ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 129
- Skrypty
- 23
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 23 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
- Paczka skrócona: część plików jest zbyt duża albo wykonywalna. Pełny folder jest w repozytorium.
Skrypty: assets/appearance-editor.js, assets/book-lab.js, assets/book-object.js, assets/book-preset.js, assets/clean-shell.js, assets/components-lab.js, assets/halftone-entry/entry.js, assets/ink-theme/ink-theme.js
Co robi i kiedy
Koordynuje specjalistów od designu i wybiera umiejętność do interfejsu, kolorów, marki lub audytu, składając wspólny brief.
Oryginalny opis (EN)
Coordinate design specialists to create, refine, adapt, or audit interfaces, visual systems, and brand assets. Refine unclear design prompts through progressive questions and a shared brief. Select the internal interface, color/layout, product, 3D, graphs, motion, platform, brand, reference, handoff, or validation skill for each case. Find saved patterns by capability and adapt them to the destination identity without requiring source-project names. Also use to reuse approved components in another project; not for isolated backend work.
Jak działa
- Reuse the repertoire without a project name
- How to coordinate
- Internal skills by use case
- Forma owns the workflow
- Preserve approved mechanisms
- Shared criteria
- Simple usage examples
- Maintenance
Podgląd SKILL.md
--- name: forma description: "Coordinate design specialists to create, refine, adapt, or audit interfaces, visual systems, and brand assets. Refine unclear design prompts through progressive questions and a shared brief. Select the internal interface, color/layout, product, 3D, graphs, motion, platform, brand, reference, handoff, or validation skill for each case. Find saved patterns by capability and adapt them to the destination identity without requiring source-project names. Also use to reuse approved components in another project; not for isolated backend work." metadata: version: 1.36.0 --- # Forma One entry point to the system: understand the request, select a specialty, read its instructions and relevant references, complete the authorized work, and verify the result. Respond in the user's language; preserve the brand, stack, data, components, and approved decisions. Do not promise perfection or universal coverage. To install, update, inspect the distribution, or distinguish the standalone skill from the plugin, consult [plugin operation](references/plugin-operation.md). Forma's visual identity belongs to the tool; it never replaces the identity of the project being served. To turn references into reusable technical knowledge, route the work to the `reference` module and the [experience protocol](references/experience-library.md): source -> evidence -> mechanism -> adaptation -> test, preserving licenses and limits. Coordination also covers websites: finding references, investigating their techniques, and creating or refining the destination site. In research involving several sources, `reference` gathers evidence; the coordinator selects a coherent direction and routes decisions to the relevant specialists. Follow [site coordination](references/experience-library.md#coordinate-reference-sites-and-the-destination-site). Do not end a creation request with a list of links. External candidate lookup matches names and URLs; topic queries suggest research guides separately. For specific recorded features, use the separate `--observed` collection and read the returned claim, date, conditions, and caveats. Its six sources and ten observed claims do not establish that all 202 sites or 2,079 portfolios were studied. A guide assignment is an investigation lens, not proof that a site has that feature. State the question and unknowns before selecting candidates. Evaluate retrieval, routing, implemented output and repeatability separately; a valid plan or a large catalog does not prove design quality. For the approved closed book, route to [the complete book integration](references/book-integration.md): BookPreset, font, stage, loader, lighting and reset travel together. Do not substitute bare engine defaults or the passport demo. ## Reuse the repertoire without a project name For creation, refinement or transfer, consider saved capabilities by the task they solve. The user does not need to mention a source project. Read [capability reuse](references/capability-reuse.md), query the relevant generic phrase, and preserve the destination's identity, components and stack. Bind semantic colors, typography and assets to that project; keep the selected mechanism's state and interaction contracts. Exact reproduction remains an explicit exception. A local correction does not activate every available pattern or authorize changes to other projects. ## How to coordinate 1. **Identify the real task:** preserve the requested operation and inspect existing context; an explanation or audit does not authorize edits. Before routing broad creation, **read [material scope](references/progressive-brief.md#material-scope), even when the brief appears complete**, and identify the user instruction or approved brief that defines the task and delivery. Route by the first applicable condition: - **Local correction:** execute the scoped change using its existing contract; no interview or new records. - **Broad creation, primary task unknown:** use Product to ask one **open question about the activity** before proposing a workflow or delivery options. Wait for the answer. - **Primary task known, delivery uncertain:** use Product to offer options with consequences, a recommendation justified by that known task, and a visible free-response path. - **Complete broad request:** record the known decisions in the relevant project records and execute without an interview. 2. **Select the primary internal skill from the table below and read its `SKILL.md`.** Start with the predominant task, not every word mentioned. Read the references selected by that specialist; a link alone is not consultation. For a small adjustment, one specialist and the reference addressing the defect may be enough. 3. **Add support only for a distinct need.** For example: interface integrates the editor; foundations resolves its color; objects-3d handles explicitly requested volume. For composition, precedence, ambiguous tasks, and fallback, use [routing and coordination](references/routing.md). Avoid opening the entire library or chaining specialists without a new question. For a new surface or broad visual refinement, establish the [shared visual foundation](references/visual-system.md#coordinate-the-foundation) before splitting work. Interface or Brand can apply it directly; add Foundations for unresolved system decisions. For new interactive designs, also read [Motion](skills/motion/SKILL.md) and implement the [default motion layer](references/motion.md#default-motion-for-new-interactive-designs), with intensity adapted to the brief. Carry the same roles and rules into each specialist. Additional expressive detail and 3D remain conditional; a local fix does not activate a redesign. 4. **Execute; do not stop at a referral.** If the user requested implementation, specialist selection is an internal step. If they only asked which one to use, deliver the recommendation. For broad work, follow the [shared workflow](references/workflow.md) and [relevant playbook](references/playbooks.md); for a local adjustment, keep the scope local. 5. **Close the loop in the destination:** verify the files actually loaded, the affected interactions, and acceptance. A repeated revision marker does not prove that CSS/JS is current; check the identity of affected resources and preserve unsaved changes before any reload. Confirm [available local checks](references/verification.md#available-local-checks) before running a validator: `npx` and `npm exec` may access the registry and are not offline availability probes. Respect explicit no-network/no-install limits; do not fetch a validator just to complete a checklist. The validation specialist supports broad audits; all work requires proportionate verification even without loading another skill. Report only observed check results, not success inferred from a skipped command or an ignored failure. Reconcile the final message with the current artifact, decision history and any delivery checkpoint. When changing an approved decision or resuming a shared brief, read [correction and resumption](references/progressive-brief.md#correct-and-resume-without-restarting) before editing. For a changed decision, append its previous value -> replacement and affected dependents before updating the current table. Whenever an existing brief is edited, also update or add its consolidated execution prompt in that record, even for a narrow correction. Before declaring completion, reread the saved history and prompt to confirm they agree with the current decisions; a successful patch alone is not evidence. A local padding fix that changes no approved decision and needs no brief edit does not require this workflow or a new brief. Before the first question or substantive work, explain the next concrete task and its purpose in one short sentence, in the user's language: "I will organize the goal and delivery type, then consolidate your prompt" or "I will adjust the sidebar navigation, then check its spacing." Identify the specialty internally; module names are optional in the message. For multi-stage work and a meaningful handoff, follow the [visible journey](references/workflow.md#visible-journey): say what is resolved, what happens next and why, without announcing a dispatch that did not occur. Do not require a fixed questionnaire or knowledge of module names. Clarify only unresolved choices that change the result, using native question controls when available or the equivalent numbered text. Once aligned, summarize and execute the requested work without an extra mandatory confirmation. A prompt-only request ends with the improved prompt. The coordinator retains context and resolves conflicts; specialists do not recursively call the coordinator. Reading a skill does not automatically create a subagent or execute a plugin. Read the chosen specialist in full; in canonical references, locate the relevant section and read enough context to apply the contract correctly. Do not recursively follow their links by default. For a local gap, this may limit reading to the spatial relationship and affected verification section; for a complete editor, include state and persistence contracts. ## Internal skills by use case | Predominant case | Skill to read | Expected outcome | |---|---|---| | Color, contrast, spacing, centering, grids, typography, or tokens | [Forma Foundations](skills/foundations/SKILL.md) | Visual relationships and values connected to real consumers | | Clean backgrounds, sidebars, buttons, inputs, search, themes, settings, and profiles | [Forma Interface](skills/interface/SKILL.md) | Composition and functional controls in the existing stack | | Prompt refinement, incomplete briefs, research, journeys, onboarding, flows, or product direction | [Forma Product](skills/product/SKILL.md) | Progressive alignment, shared decisions, consolidated prompt and appropriate delivery | | Books, covers, passports, mascots, volume, materials, gloss, or relief | [Forma Objects 3D](skills/objects-3d/SKILL.md) | The requested mechanism, verifiable material, and interaction | | Graphs, backlinks, Canvas, maps, dashboards, or time-series data | [Forma Graphs & Data](skills/graphs-data/SKILL.md) | Relationships and visualizations with sources, meaning, and controls | | Gestures, transitions, animation, video, film, or reduced motion | [Forma Motion](skills/motion/SKILL.md) | Interactive motion or a rendered sequence with continuity and its own acceptance criteria | | Behavior specific to web, mobile, desktop, installers, or devices | [Forma Platforms](skills/platforms/SKILL.md) | Task and operational adaptation to the target environment | | Identity, campaigns, marketing landing pages, assets, presentations, or print | [Forma Brand](skills/brand/SKILL.md) | Message, composition, and deliverables for the requested channels | | Finding examples, selecting references, reverse engineering, technologies, or fidelity differences | [Forma Reference](skills/reference/SKILL.md) | Contextual research, evidence separated from hypotheses, and transferable specifications | | Quality audits, accessibility, regression, or rendered acceptance | [Forma Validation](skills/validation/SKILL.md) | Bounded findings/evidence and fixes when authorized | | Editable design sources, exports, libraries, design-to-code, or technical delivery | [Forma Handoff](skills/handoff/SKILL.md) | Source, components, and output delivered and verified | Identifiers follow `forma-<specialty>`, for example `$forma-motion`, `$forma-interface`, and `$forma-objects-3d`. They can be called directly when the environment catalog offers them. The `$forma` entry point still selects and reads modules through the paths above, without relying on discovery in every host. Do not invent an `invoke_skill` tool command: use the reading/invocation mechanism actually available in the environment. ## Forma owns the workflow All design decisions route through the internal specialists and canonical contracts above. Do not forward a design responsibility to a named external skill or make another plugin a prerequisite. For a missing method, use Reference to investigate, the relevant domain specialist to adapt it, and Validation to check the result. Preserve technical dependencies actually required by the implementation. Tools provide execution capabilities, not a replacement coordinator. Select an available file reader, browser, design canvas, renderer or artifact inspector through the [tool capability contract](references/integrations.md). Verify the real API, connection and result; the package does not contain or install those runtimes. Do not start paid generation merely to complete a checklist. For production jobs, resumption or an explicitly requested separate runtime, use [coordinated production](references/agent-production.md). A described workflow does not prove execution. When authorized delegation is useful, assign the question, files and acceptance criteria and avoid concurrent edits; it is not required for every task. ## Preserve approved mechanisms When examples are needed, use the [searchable library](references/reference-library.md): original cards covering Forma resources and patterns, a site index associated with original investigation cases, context-based selection, visual browsing, and optional credited media research. Read only relevant candidates; a pattern card does not prove its execution in the consumer. A local correction does not require inspiration research. The library does not replace the consumer's approved mechanism. Distinguishing **applying principles** from **reusing a mechanism** is mandatory for transfer requests. Adapting brand/content does not authorize replacing volume with tilted CSS or a manipulable editor with three fixed colors. If the request is **identical to the approved implementation**, also preserve its composition, palette, and responsive behavior: the explicit instruction takes precedence over generic brand adaptation. Use the final cascade and rendered state of that revision, not just an earlier specification. Preserve the destination's data, routes, and content. Follow [consumer reuse](references/playbooks.md#h-reuse-capabilities-in-another-project): contract -> available implementation -> consumer -> observed distinguishing operation. For an approved reproduction, freeze criteria before changing the destination and use [fidelity contracts](references/fidelity-contracts.md). The portable verifier compares measurements against the frozen reference; differences, missing data, or an unconfirmed revision prevent declaring fidelity complete. Do not generate expected values from the destination itself or widen tolerances to make a test pass. | Resource | Package status | Route | |---|---|---| | Clean interface foundation | Scoped CSS + HTML/JS example with in-memory data | Interface -> [recipe](references/clean-shell.md) | | Integral Soft Glass reproduction | Separate local approved source, media, fonts and motion; verify its manifest before reuse | Reference + Brand -> [integral kit](references/soft-glass-integral.md) | | Soft Glass visual kit | Scoped CSS, paired themes, complete nine-section landing plus footer, and workspace/control specimen; no product handlers | Interface + Brand -> [visual preset](references/soft-glass.md) | | BookObject and color helper | Original reusable code; volume requires a valid Three loader, and static mode is separate | Objects 3D -> [contract](references/reusable-objects.md) and [approved case](references/book-polish-case-study.md) | | Articulated passport | Executable NeuronPassport preserves the approved CSS engine and visual layers; Three PassportObject is a separate legacy alternative | Objects 3D -> [extracted component](references/reusable-components.md#neuronpassport-integration) and [approved CSS case](references/passport-polish-case-study.md) | | Appearance/lighting editor | Executable vanilla `AppearanceEditor`, scoped styles and save/cancel adapters; compact profile guides consumer fidelity | Interface -> [component](references/reusable-components.md#appearanceeditor-integration), [editor contract](references/lighting-editors-icons.md) and [material profile](references/adaptive-visual-systems.md) | | Component lab | Runnable appearance/passport consumer with real renderer diagnostics and explicit dependency loader; not automatic framework integration | [Setup and evidence limits](references/reusable-components.md#run-the-lab) | | Contrast, layout, and evidence verifiers | Local scripts with bounded scope | Validation -> [executable resources](references/resources.md) | Do not depend on the authoring project's folder or presumed files from another chat. Check the resource in the installed version. Package tests do not prove consumer integration. Preserve hashes and audit limits when transferring an approved result. ## Shared criteria Correctness, security, access, and data come before polish. Preserve the existing system and identity; do not impose styles, 3D, tools, or frameworks by association. Standards, heuristics, and preferences are different categories; resolve conflicts through [precedence](references/conflicts.md). Test the task, focus, extreme content, and affected states. Static/bundle analysis, observed UI, physical devices, exported files, and publication provide distinct evidence. For a skill release, comparative trial, or reuse audit, use [release validation](references/release-validation.md): freeze inputs, preserve independent submissions, and report browser, input, motion, WebGL, persistence, retrieval, and cost gates separately. A reference does not grant authorship, asset licenses, or authorization to publish. [Verification](references/verification.md) and the [rendered cycle](references/rendered-validation.md) define how to complete acceptance; [templates](references/templates.md) are optional, not bureaucracy for small adjustments. ## Simple usage examples - "Use $forma to refine my design request. Resolve missing choices one at a time, preserve what I already decided, then build the agreed design." - "Use $forma to improve this prompt only. Use my references as evidence and return a standalone brief I can use with another assistant." - "Use $forma to apply the clean interface foundation to my app while preserving its brand, stack, and routes." - "Use $forma and the integral Soft Glass local kit to preserve the complete approved landing, its fonts, media and motion; verify the manifest and copy before adapting." - "Use $forma to reuse the complete Soft Glass landing, including its narrative sections, halftone hero, FAQ, contact and footer; design only in light/dark and mobile." - "Use $forma and Soft Glass for a design-only landing and workspace: dotted sidebar, inset rounded panel, glass buttons and account footer, in light/dark and desktop/mobile." - "Use $forma to fix the alignment and colors in this form." - "Use $forma to reuse the approved closed book through BookPreset, preserving its framing, light, materials, and gestures." - "Use $forma to integrate the approved interactive passport through NeuronPassport, preserving its opening, page turns, editing, and save behavior." - "Use $forma to implement the complete lighting editor with pools, save/reopen behavior, and colors by context." - "Use $forma to audit this flow; do not edit it yet." - "Use $forma to create a campaign and deliver editable files." - "Use $forma to create a clean PDF guide with cards and comparison tables. Preserve our branding and facts, deliver the PDF, and inspect every exported page." - "Use $forma-motion to refine this interface's animations." - "Use $forma-interface to apply the sidebar, clean background, and controls to my app." ## Maintenance Keep all Forma-authored package content in US English with ASCII editorial punctuation, following the [editorial and encoding standard](references/reference-library.md#editorial-and-encoding-standard). Preserve original identities, licenses, URLs and intentional multilingual behavior. This package policy does not change the user's language or the destination product's locale. For new content, follow [authorship and integration](references/authorship.md): write a solution to a real problem, connect it to the resource, and verify it; renaming external content does not make it original. When replacing imported content, preserve the capabilities learned and verify where they belong in Forma's own contracts, including coordination, research, direction, and refinement. References, standards, dependencies, and media retain their origins. When improving this skill, keep the entry point small, give each specialist a distinct responsibility, and keep theory in its canonical reference. Keep each capability linked to its implementation, contract and evidence in the [resource map](references/sources.md). Validate the structure and [decision scenarios](evals/scenarios.md), including [routing](evals/routing-scenarios.md) and [progressive briefing](evals/progressive-brief-scenarios.md). Reading, documentary evaluation, and product execution are not interchangeable proof. To incorporate findings from a conversation or reconcile a new plan with approved design, use [approved product evolution](references/approved-product-evolution.md): distinguish local decisions, transferable mechanisms, and evidence. Do not copy entire conversations, personal data, or one product's requirements into universal defaults. For splash-to-sidebar entry and fine/coarse halftone textures, use Motion + Reference and the [halftone entry kit](references/halftone-entry.md). This is an opt-in reusable adaptation, not a default loading screen. When a new visual direction calls for expressive brand entry, print texture or an organic landscape, briefly suggest this kit as one contextual option using the [adaptation and suggestion rules](references/halftone-entry.md#adaptation-and-contextual-suggestions). Preserve the destination identity and do not repeat a declined suggestion.
Pliki w paczce (129)
- LICENSE 1 KB
- SKILL.md 22 KB
- THIRD_PARTY_NOTICES.md 3 KB
- agents/openai.yaml 1 KB
- assets/appearance-editor.css 9 KB
- assets/appearance-editor.js 30 KB
- assets/book-lab.css 3 KB
- assets/book-lab.html 4 KB
- assets/book-lab.js 5 KB
- assets/book-object.js 41 KB
- assets/book-preset.js 3 KB
- assets/clean-shell.css 25 KB
- assets/clean-shell.html 11 KB
- assets/clean-shell.js 19 KB
- assets/clear-pdf-guide.html 3 KB
- assets/components-lab.css 5 KB
- assets/components-lab.html 3 KB
- assets/components-lab.js 6 KB
- assets/evidence.example.json 1 KB
- assets/layout.example.json 1 KB
- assets/library-colors.js 4 KB
- assets/neuron-passport.js 15 KB
- assets/operational-icons.svg 10 KB
- assets/passport-object.css 1 KB
- assets/passport-object.js 20 KB
- assets/reference-browser.css 7 KB
- assets/reference-browser.html 4 KB
- assets/reference-browser.js 18 KB
- assets/tokens.example.json 1 KB
- assets/audits/book-polish-2026-10-26/manifest.json 3 KB
- assets/audits/book-transfer-2026-10-29/manifest.json 2 KB
- assets/audits/passport-polish-2026-10-27/manifest.json 4 KB
- assets/fonts/Inter-OFL.txt 4 KB
- assets/fonts/inter-latin-opsz-normal.woff2 71 KB
- assets/halftone-entry/entry.css 2 KB
- assets/halftone-entry/entry.js 4 KB
- assets/halftone-entry/preview.html 3 KB
- assets/ink-theme/ink-theme.css 1 KB
- assets/ink-theme/ink-theme.js 4 KB
- assets/ink-theme/preview.css 2 KB
- assets/ink-theme/preview.html 2 KB
- assets/ink-theme/preview.js 1 KB
- assets/ink-theme/validation.json 7 KB
- assets/neuron-passport/data.js 18 KB
- assets/neuron-passport/frame.css 3 KB
- assets/neuron-passport/frame.html 1 KB
- assets/neuron-passport/frame.js 10 KB
- assets/neuron-passport/icons.js 11 KB
- assets/neuron-passport/lighting.js 15 KB
- assets/neuron-passport/passport-catalog.js 38 KB
- assets/neuron-passport/passport-motion.js 49 KB
- assets/neuron-passport/passport.css 42 KB
- assets/neuron-passport/passport.js 31 KB
- assets/neuron-passport/profile.css 34 KB
- assets/neuron-passport/source-manifest.json 3 KB
- assets/neuron-passport/styles.css 60 KB
- assets/plugin-brand/README.md 8 KB
- assets/plugin-brand/icon-dark.svg 1 KB
- assets/plugin-brand/icon.svg 1 KB
- assets/plugin-brand/identidade.html 12 KB
- assets/plugin-brand/identity.css 13 KB
- assets/plugin-brand/logo.png 2 KB
- assets/plugin-brand/preview-mobile-top.png 186 KB
- assets/plugin-brand/preview-symbols.png 61 KB
- assets/plugin-brand/preview-usage.png 32 KB
- assets/plugin-brand/provenance.json 3 KB
- assets/plugin-brand/qa.json 18 KB
- assets/plugin-brand/tokens.css 1 KB
- assets/plugin-brand/tokens.json 3 KB
- assets/plugin-brand/verify.cjs 10 KB
- assets/plugin-brand/wordmark-dark.svg 1 KB
- assets/plugin-brand/wordmark.svg 1 KB
- assets/reference-library/catalog.json 91 KB
- assets/reference-library/observed-experiences.json 21 KB
- assets/reference-library/portfolio-import.json 3 KB
- assets/reference-library/site-index.json 88 KB
- assets/reference-profiles/compact-appearance-v1.fidelity.json 120 KB
- assets/reference-profiles/compact-appearance-v1.json 13 KB
- assets/reference-profiles/desktop-material-reference-v1.json 60 KB
- assets/reference-profiles/helloura-experience.json 13 KB
- assets/reference-profiles/kimi-2026-10-26.json 6 KB
- assets/reference-profiles/seuimposto-2026-10-25.json 3 KB
- assets/reference-profiles/soda-2026-10-26.json 8 KB
- assets/soft-glass/README.md 5 KB
- assets/soft-glass/calm-navigation.json 5 KB
- assets/soft-glass/landing-README.md 10 KB
- assets/soft-glass/landing-profile.json 6 KB
- assets/soft-glass/landing-validation.json 10 KB
- assets/soft-glass/landing.css 51 KB
- assets/soft-glass/landing.html 51 KB
- assets/soft-glass/landing.js 5 KB
- assets/soft-glass/preview.html 14 KB
- assets/soft-glass/preview.js 1 KB
- assets/soft-glass/soft-glass.css 19 KB
- assets/soft-glass/tokens.json 3 KB
- assets/soft-glass/validation.json 11 KB
- assets/soft-glass/captures/controls-dark-1440.png 106 KB
- assets/soft-glass/captures/controls-dark-390.png 99 KB
- assets/soft-glass/captures/controls-dark-focus.png 107 KB
- assets/soft-glass/captures/controls-dark-hover.png 105 KB
- assets/soft-glass/captures/controls-dark-pressed.png 105 KB
- assets/soft-glass/captures/controls-light-1440.png 110 KB
- assets/soft-glass/captures/controls-light-390.png 103 KB
- assets/soft-glass/captures/controls-light-focus.png 111 KB
- assets/soft-glass/captures/controls-light-hover.png 110 KB
- assets/soft-glass/captures/controls-light-pressed.png 110 KB
- assets/soft-glass/captures/landing-dark-1440.png 124 KB
- assets/soft-glass/captures/landing-dark-390.png 93 KB
- assets/soft-glass/captures/landing-light-1440.png 134 KB
- assets/soft-glass/captures/landing-light-390.png 103 KB
- assets/soft-glass/captures/workspace-dark-1440.png 188 KB
- assets/soft-glass/captures/workspace-dark-390.png 106 KB
- assets/soft-glass/captures/workspace-light-1440.png 133 KB
- assets/soft-glass/captures/workspace-light-390.png 83 KB
- assets/soft-glass/captures/landing/1440-dark-audience.png 135 KB
- assets/soft-glass/captures/landing/1440-dark-contact.png 432 KB
- assets/soft-glass/captures/landing/1440-dark-features.png 167 KB
- assets/soft-glass/captures/landing/1440-dark-footer.png 320 KB
- assets/soft-glass/captures/landing/1440-dark-how.png 115 KB
- assets/soft-glass/captures/landing/1440-light-audience.png 136 KB
- assets/soft-glass/captures/landing/390-dark-audience.png 72 KB
- evals/progressive-brief-scenarios.md 23 KB
- evals/release-validation.md 7 KB
- references/accessibility.md 4 KB
- references/agent-production.md 8 KB
- skills/brand/agents/openai.yaml 1 KB
- skills/foundations/agents/openai.yaml 1 KB
- skills/graphs-data/agents/openai.yaml 1 KB
- skills/handoff/agents/openai.yaml 1 KB
Pominięte w paczce: 141 (zbyt duże albo wykonywalne), są w repozytorium.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · figueirego/forma | 100 | MIT |
| FormaMindPro/formamind | 100 | MIT |
| figueirego/forma | 100 | MIT |
| figueirego/forma | 100 | MIT |
| figueirego/forma | 100 | MIT |
| Pukhaan/forma-board | 100 | AGPL-3.0 |
| namzug16/forma | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f4679bcb311a (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
- 90brand-identity
Tworzy brief tożsamości wizualnej marki: kierunek logo, paletę kolorów, typografię, styl obrazów i podstawy systemu projektowego dla projektanta lub agencji. - 90forma-product
Doprecyzowuje niejasne prośby projektowe w briefy i gotowe polecenia, bada zadania użytkowników i projektuje przepływy produktu z proporcjonalnym researchem. - 90forma-product
Doprecyzowuje niejasne prośby projektowe w briefy i gotowe polecenia, bada zadania użytkowników i projektuje przepływy produktu z proporcjonalnym researchem. - 90brand-identity
Tworzy brief tożsamości wizualnej marki: kierunek logo, paleta kolorów, typografia, styl obrazów i podstawy systemu projektowego, na przykład dla projektanta lub agencji. - 85form
Działa jako projektant wizualny: tożsamość marki, systemy kolorów, typografia, tokeny designu i projekt UI. - 100web-design-expert
Tworzy unikalne projekty stron z tożsamością marki, paletami kolorów, typografią, nowoczesnymi wzorcami UI i UX, układem i responsywnością.