设计与前端
4,640 个结果
- Game Art DirectorAlterLab Creative Technologies LaboratoryInvoke when the user asks about art style, visual language, style guide, character design, environment art, UI art direction, asset pipeline, reference boards, color palette, or shape language. Triggers on: "art style", "visual", "style guide", "character design", "environment art", "asset pipeline", "color palette", "shape language".
- Game Audio DirectorAlterLab Creative Technologies LaboratoryInvoke when the user asks about sound design, music direction, audio identity, adaptive audio, spatial audio, SFX, sonic palette, dialogue systems, audio middleware, dynamic music, or sound bible creation. Triggers on: "sound design", "music", "audio", "SFX", "adaptive audio", "spatial audio", "sonic palette", "FMOD", "Wwise", "sound bible".
- Game BrainstormAlterLab Creative Technologies LaboratoryInvoke when the user wants to brainstorm game ideas, explore concepts, run structured ideation, or develop a new game concept from scratch. Triggers on: "game idea", "brainstorm", "concept", "ideation", "what if", "game concept", "pitch". Do NOT invoke for reviewing existing designs (use game-design-review) or market analysis (use game-market-research). Part of the AlterLab GameForge collection.
- Game Code ReviewAlterLab Creative Technologies LaboratoryInvoke when the user wants a game-specific code review, architecture check, or technical analysis of game code. Covers frame independence, hot path performance, state machine integrity, and resource lifecycle. Triggers on: "code review", "review my code", "check architecture", "game code quality".
- Game Creative DirectorAlterLab Creative Technologies LaboratoryInvoke when the user asks about creative vision, game pillars, core fantasy, design direction, art style decisions, scope arbitration, or creative conflicts. Triggers on: "vision", "pillars", "creative direction", "core fantasy", "tone", "aesthetic", "creative conflict". Do NOT invoke for mechanics design (use game-designer) or technical architecture (use game-technical-director).
- Game Design ReviewAlterLab Creative Technologies LaboratoryInvoke when the user wants feedback on a game design document, GDD review, design evaluation, or consistency check on an existing design. Triggers on: "review my GDD", "design feedback", "evaluate design", "design document review", "GDD critique". Do NOT invoke for brainstorming new ideas (use game-brainstorm) or balance tuning (use game-balance-check). Part of the AlterLab GameForge collection.
- Game DesignerAlterLab Creative Technologies LaboratoryInvoke when the user asks about game mechanics, core loop, balance, progression, economy design, reward systems, onboarding, game feel, systems design, or GDD authoring. Triggers on: "mechanics", "core loop", "balance", "progression", "reward", "onboarding", "game feel", "systems design", "GDD".
- Game Gdd AuthorAlterLab Creative Technologies LaboratoryInvoke for guided game design document authoring -- section-by-section GDD creation with validation, pillar alignment, and scope tier marking. Triggers on: "write GDD", "create GDD", "game design document", "document my game", "GDD authoring", "fill in GDD". Do NOT invoke for reviewing an existing GDD (use game-design-review) or designing specific game systems (use game-designer).
- Game Market ResearchAlterLab Creative Technologies LaboratoryConduct market research for a game concept -- competitive landscape, market sizing, audience analysis, trend detection, and positioning strategy. Triggers on: "market research", "competitive analysis", "market sizing", "audience analysis", "is this game viable", "similar games", "market validation".
- Game Narrative DirectorAlterLab Creative Technologies LaboratoryInvoke when the user asks about story structure, branching narrative, dialogue systems, world-building, character design, environmental storytelling, ludonarrative coherence, writing for games, lore, theme, or character arcs. Triggers on: "story", "narrative", "dialogue", "lore", "world-building", "character arc", "branching", "ludonarrative".
- Game PostmortemAlterLab Creative Technologies LaboratoryRun a structured post-mortem analyzing what went well, what went wrong, and extractable lessons. Pulls git history, milestone data, and retrospective notes automatically. Triggers on: "post-mortem", "project review", "what did we learn", "lessons learned", or when a major milestone or project is complete.
- Game RetrospectiveAlterLab Creative Technologies LaboratoryRun a game development post-mortem rooted in the GDC tradition. Triggers on: "retrospective", "retro", "post-mortem", "lessons learned", "what went right", "what went wrong", "kill list review". Do NOT invoke for design document review (use game-design-review) or playtesting (use game-playtest). Part of the AlterLab GameForge collection.
- Game Reverse DocumentAlterLab Creative Technologies LaboratoryGenerate documentation from existing code or prototypes. Triggers on: "document this", "reverse document", "generate docs from code", "onboard to codebase", "document existing system". Do NOT invoke for writing new design docs from scratch (use game-brainstorm or game-design-review). Part of the AlterLab GameForge collection.
- Game Unity SpecialistAlterLab Creative Technologies LaboratoryInvoke when the user works with Unity or asks about C#, MonoBehaviour, DOTS/ECS, Shader Graph, Addressables, UI Toolkit, URP/HDRP, or ScriptableObjects. Triggers on: "Unity", "MonoBehaviour", "DOTS", "ECS", "Shader Graph", "Addressables", "UI Toolkit", "URP", "HDRP", "ScriptableObject", ".unity", ".cs".
- Mobbin SearchmobbinSearch Mobbin for real app UI screenshots and visually analyze them. Required before calling the `search_screens` MCP tool — this skill defines how to plan searches, respond, and build HTML evidence boards when the screens are the answer.
- Vtex Io Admin ReactvtexApply when building VTEX IO admin-facing React interfaces under the admin builder. Covers VTEX Styleguide and Shoreline usage, admin page composition, data-heavy admin interactions, and keeping administrative interfaces consistent with the VTEX Admin environment. Use for settings pages, moderation tools, dashboards, or operational UIs inside VTEX Admin.
- Vtex Io App SettingsvtexApply when defining, validating, or consuming VTEX IO app settings. Covers settingsSchema, app-level configuration boundaries, and how backend or frontend code should depend on settings safely. Use for merchant-configurable behavior, settings forms, or reviewing whether settings belong in app configuration rather than hardcoded logic or custom data entities.
- Vtex Io Auth And PoliciesvtexApply when deciding or implementing permissions and authorization boundaries for VTEX IO apps. Covers manifest policies, outbound-access rules, least-privilege design, and how service routes or integrations map to explicit permissions.
- Vtex Io Client IntegrationvtexApply when designing or implementing how a VTEX IO backend app integrates with VTEX services or external APIs through @vtex/api and @vtex/clients. Covers choosing the correct client type, registering clients in IOClients, configuring InstanceOptions, and consuming integrations through ctx.clients.
- Vtex Io Events And WorkersvtexApply when designing or implementing asynchronous processing in VTEX IO services through events, workers, and background handlers. Covers event handler structure, idempotency, retry-safe processing, and moving expensive work out of request-response routes. Use for event-driven integrations, delayed processing, or background jobs in VTEX IO apps.
- Vtex Io Http RoutesvtexApply when designing or implementing HTTP endpoints exposed by a VTEX IO backend service. Covers route boundaries, handler structure, middleware composition, request validation, and response modeling for service.json routes. Use for webhook endpoints, partner integrations, callback APIs, or reviewing VTEX IO handlers that should expose explicit HTTP contracts.
- Vtex Io React AppsvtexApply when building React components under react/ or configuring store blocks in store/ for VTEX IO apps. Covers interfaces.json, contentSchemas.json for Site Editor, VTEX Styleguide for admin apps, and css-handles for storefront styling. Use for creating custom storefront components, admin panels, pixel apps, or any frontend development within the VTEX IO react builder ecosystem.
- Vtex Io Render Runtime And BlocksvtexApply when connecting React components to Store Framework blocks and render-runtime behavior in VTEX IO. Covers interfaces.json, block registration, block composition, and how storefront components become configurable theme blocks. Use for block mapping, theme integration, or reviewing whether a React component is correctly exposed to Store Framework.
- Vtex Io RootpathvtexApply when building VTEX IO apps that must work correctly in multi-binding stores where bindings use path prefixes (e.g. store.com/us/, store.com/br/). Covers rootPath extraction from x-vtex-root-path header, useRuntime().rootPath in React, URL construction in backends, link generation, asset paths, and API route considerations.