Art & Design

Make finished App Store screenshot sets from raw screenshots — brand-colour gradient and white (or a dark-dominant dark theme) flowing as one panorama across the images, big centred heavy headlines, a device at a fixed spot with its screen dimmed while a cropped part pops out past it, and glossy puffy 3D objects from the app's own context (a crescent and stars for a prayer app, speech bubbles for a subtitle app) on the seams, with a phone-less hero where the app's symbol is a giant 3D object holding its own UI cards. Covers every required iPhone size (6.9" and 6.3") and the iPhone Duo outer and inner displays, in light and dark (from light- and dark-mode screenshots if given), rendered with an HTML template and headless Chrome; the UI stays pixel-exact. Use when the user asks for App Store / store screenshots, iPhone Duo screenshots, or a dark-theme screenshot set from raw screenshot folders, or names this skill. Produces the sets directly, with no plan files or approval stops.

Art-directs and builds websites, landing pages, app screens and decks from real references in the Inspiration library by VASA.Works (via its MCP server). Researches and views references, writes a specimen sheet and a design direction, builds, then screenshots the build and fixes it against the references. Use when the user wants a page designed, redesigned or restyled, or says the result looks generic or templated.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Hand the current conversation off to a fresh background agent that picks up the work immediately.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".

Ask which skill or flow fits your situation. A router over the skills in this repo.

Pursue a long-running goal in a single session by co-ordinating subagents.

Add a filterable, project-based showcase catalog to a personal or company site — the pattern where every project is one card that opens a detail page, and visitors filter by the KIND of project (a launched product vs a hackathon build vs an R&D experiment). Use when someone wants to build a portfolio / projects / "things I've built" page, a showcase grid with filters, or wants to add one new project to an existing showcase and isn't sure how to categorize or present it. Interviews you about your stack and what you already have before writing anything.

Unity-based mini colony-sim-style game prototype, built using game-dev-agent. Portfolio piece demonstrating AI agent + game dev T-shape skill.

Multi-chain wallet portfolios: token balances, tx history, DeFi positions, NFTs. Use when inspecting any EVM address (e.g. show vitalik.eth balances, decode this tx, what DeFi protocols does 0x... use).

Kuvera portfolio & market data CLI. Query mutual fund data, gold prices, USD/INR rates, fund category returns, and user portfolio info from Kuvera. Use when the user asks about their investments, mutual funds, gold prices, market overview, or Kuvera portfolio.

Personal developer blog and portfolio design with a narrow reading column, serif post text, warm neutrals and one green accent, light and dark mode with a toggle, writing grouped by year, reading time, post outline, author box, previous and next posts, project tiles with tech pills and an experience timeline.

Connect to your Aiqbee knowledge graph via MCP. Search, create, and link neurons across your architecture, portfolio, and digital strategy brains.

Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios, and portfolios that convert visitors into opportunities.

Build portfolio websites with mini app, doc, and whiteboard. Use when asked about "portfolio", "showcase my work", "portfolio website", "design portfolio", "project portfolio", or "build my portfolio".

>- Deterministic, Token-Zero project onboarding engine for Aaradhya's portfolio website (AaradhyaDT.github.io). Use whenever asked to add, register, or document a new project, tool, or build in the portfolio. Prevents manual HTML text slicing and guarantees automatic ID numbering, AES-256-GCM link encryption into access.js, filter pill recounting, and zero-token verification.

Identifies a user's visual preferences from described examples, extracts the defining characteristics including color treatment, contrast, subject selection, and composition, and produces a personal photography style guide with specific settings targets. Applicable to any camera and processor. Use when the user asks to develop a photography style, create visual consistency, define their aesthetic, or build a cohesive portfolio look. Do NOT use for single-photo composition (use composition-guide), camera settings for a specific shot (use exposure-triangle), or photo editing steps (use photo-editing-workflow).

Balance visual design with ATS compatibility for creative roles

Use this skill to generate well-branded interfaces and assets for James Notley — Materials Engineer (portfolio website and PDF dossier), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for protoyping.

Prepare Azure apps for deployment (infra Bicep/Terraform, azure.yaml, Dockerfiles). Use for create/modernize or create+deploy; not cross-cloud migration (use azure-cloud-migrate). WHEN: \"create app\", \"build web app\", \"create API\", \"create serverless HTTP API\", \"create frontend\", \"create back end\", \"build a service\", \"modernize application\", \"update application\", \"add authentication\", \"add caching\", \"host on Azure\", \"create and deploy\", \"deploy to Azure\", \"deploy to Azure using Terraform\", \"deploy to Azure App Service\", \"deploy to Azure App Service using Terraform\", \"deploy to Azure Container Apps\", \"deploy to Azure Container Apps using Terraform\", \"generate Terraform\", \"generate Bicep\", \"function app\", \"timer trigger\", \"service bus trigger\", \"event-driven function\", \"containerized Node.js app\", \"social media app\", \"static portfolio website\", \"todo list with frontend and API\", \"prepare my Azure application to use Key Vault\", \"managed identity\".

Build and optionally publish a GitHub Pages developer portfolio and GitHub profile README from a user-uploaded LinkedIn profile PDF/export or pasted LinkedIn profile text. Use when the user asks to generate a portfolio website, profile README, GitHub Pages repo, or developer-portfolio config from LinkedIn data, especially when they mention LinkedIn PDF/export, GitHub CLI, gh auth, portfolio publishing, or the developer-portfolio template.