All authors
Claude Skills by ainurdev
github.com/ainurdev23 skills0 installs31 views
- Accessibility AuditUse when checking a UI against WCAG basics — keyboard, contrast, semantics, and announced state.Votes: 0GitHub stars: 6
- Api DocsUse when documenting endpoints or a public interface — task-oriented, with real examples.Votes: 0GitHub stars: 6
- Bridge EyesUse when frontend work in this repo needs to be looked at rather than asserted — after changing anything under bridge/dashboard/web, bridge/miniapp/web or site/, or when the user says "screenshot it", "does it look right", "show me the dashboard", or asks you to verify a UI change. Covers headless capture in WSL and driving the live UIs over CDP.Votes: 0GitHub stars: 6
- Bridge Feature SliceUse when adding or changing a capability in this repo that users should reach — a new endpoint, panel, command, or piece of session data. Names every file the change has to touch across the bot, the Mini App and the dashboard, in order, so a surface doesn't get left behind. Use before writing code, not after.Votes: 0GitHub stars: 6
- Bridge ShipUse when a change to this repo needs to actually run — after editing anything under bridge/, or when the user says "restart the bridge", "is it live", "ship it", "rebuild the dashboard", or reports that a fix you already made isn't working. Covers the build/restart/verify loop and the ways restarting from inside a bridge session kills your own turn.Votes: 0GitHub stars: 6
- Bridge WorktreeUse when starting a feature, experiment or risky refactor in this repo — anything bigger than a one-file fix. Also when the user says "worktree", "new branch", "work on this in parallel", or when a change adds a table, a column or any new persisted data. Covers where the worktree goes, what is missing inside it, and keeping new data off the live bridge DB.Votes: 0GitHub stars: 6
- ChangelogUse when writing release notes — grouped by what users can now do, not by commit.Votes: 0GitHub stars: 6
- Color PaletteUse when building or fixing a palette — accessible, consistent, and legible in both themes.Votes: 0GitHub stars: 6
- Content StrategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.Votes: 0GitHub stars: 6
- Design FirstUse when the user sends /design-first <task> or presses the composer's DESIGN button — design the change before any implementation. Produces brand-system HTML mockups plus a short spec, screenshots them into the transcript, pushes the draft to the linked Claude Design project, and stops for approval; repo code changes start only after the user approves.Votes: 0GitHub stars: 6
- Design ImplementUse when the user sends /design-implement [name] — they designed something themselves in the claude.ai Design UI; pull it from the linked Claude Design project and implement it in this repo.Votes: 0GitHub stars: 6
- Design ReviewUse when critiquing a screen or component — hierarchy, spacing, states, and whether it reads as intentional.Votes: 0GitHub stars: 6
- Design TokensUse when setting up or auditing a token system — colour, spacing, radius, and type as named decisions.Votes: 0GitHub stars: 6
- Empty StatesUse when a view can be empty, slow, or broken — design the other three states, not just the happy one.Votes: 0GitHub stars: 6
- Micro InteractionsUse when adding motion or feedback — fast, purposeful, interruptible, and reduced-motion aware.Votes: 0GitHub stars: 6
- Mystical Assistant DesignUse this skill to generate well-branded interfaces and assets for Mystical Assistant — a remote-dev bridge that runs Claude Code on your machine, driven from a Telegram bot, a Telegram Mini App, and a localhost desktop dashboard. Its look is a phosphor CRT terminal HUD (teal-on-black, monospace, scanlines, corner-bracketed panels, an occult-oracle voice). Use for production work or throwaway prototypes/mocks/decks. Contains design guidelines, color/type/spacing tokens, fonts, the brand emblem...Votes: 0GitHub stars: 6
- OgilvyApply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.Votes: 0GitHub stars: 6
- Onboarding GuideUse when writing onboarding docs — get a newcomer to a working change on day one.Votes: 0GitHub stars: 6
- Typography ScaleUse when setting type — a small ramp, deliberate line height, and hierarchy that survives real content.Votes: 0GitHub stars: 6
- Visual Style PresetsPick and apply a complete visual style direction — surface ladder, type scale, accent discipline, and one signature structural motif — for a website, landing page, dashboard, or app shell. Use when asked for a specific look such as dark glass, dark technical, frosted workspace, warm paper, beige minimal, editorial grid, archival book, wireframe diagnostic, cobalt contrast, or "make it feel premium/expensive/engineered", or when a design needs a coherent direction rather than ad-hoc styling.Votes: 0GitHub stars: 6
- Beautiful ShadowsApply exact Tailwind arbitrary shadow utilities for polished, layered neutral elevation. Use when compact cards, controls, panels, popovers, hero media, feature callouts, or modal-like containers need refined shadows without default Tailwind shadow scales or colored tinting.Votes: 0GitHub stars: 6
- BrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Votes: 0GitHub stars: 6
- Landing PageUse when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services. Covers structure, layout patterns, conversion strategies, copywriting, SEO/AEO, and common pitfalls.Votes: 0GitHub stars: 6