motiful

@motiful source repo

34 skills
0 followers
10 hours ago last updated

▌
Chrome Profile Bridge · motiful
Enhanced browser automation with Chrome profile targeting. Use this skill BEFORE playwright-cli when the user needs to work with a specific Chrome profile (e.g., "open my tax site", "check my bank account", "use my work profile"). This skill handles profile selection, then hands off to playwright-cli for actual browser control.

0
installs
▌
Cloudflare Deploy Rules · motiful bundle
Cloudflare deployment hard constraints. MUST authenticate via scoped API Token in CLOUDFLARE_API_TOKEN env var (loaded from git-ignored .env), MUST bypass HTTP proxy on every Cloudflare API call (curl --noproxy '*', wrangler with NO_PROXY="*" no_proxy="*"), MUST extract account ID from /zones?name=<domain> when token lacks Account:Read and persist as CLOUDFLARE_ACCOUNT_ID. NEVER run `wrangler login` (OAuth breaks behind proxies/VPN), NEVER let a Cloudflare request traverse the local ClashX/HTTP proxy, NEVER commit credentials. Activates on any wrangler command, api.cloudflare.com call, or CLOUDFLARE_* env edit. MUST read SKILL.md BEFORE running wrangler commands, calling Cloudflare API, or editing CLOUDFLARE_* env vars.

0
installs
▌
Progress Hygiene Rules · motiful bundle
Progress file hard constraints. MUST maintain exactly one progress root per project per the location matrix, valid frontmatter with absolute dates on every progress doc, NN- numeric prefix only for time-ordered children in progress/ and research/ trees (never skill references), archive when files exceed ~200 lines preserving content verbatim, relative paths in all cross-file references. NEVER place progress under .claude/, maintain two progress files with mutual references, use relative dates, duplicate child content into parent, summarize archived content, or discard completed history. Activates on any progress file edit, migration, or new-session handoff. MUST read SKILL.md BEFORE editing, creating, moving, or archiving any progress or research tree file.

0
installs
▌
Progress Hygiene · motiful bundle
Progress tree methodology — single source of truth location matrix, frontmatter discipline, tree expansion protocol, and new-session handoff generation for project progress tracking. Use when creating a new progress file, opening a child subtree, generating a handoff prompt for a fresh session, or auditing an existing project for progress-file drift. Answers "where does the progress file live", "when do I open a child", and "how does a new session continue the work". Pairs with progress-hygiene-rules for MUST/NEVER constraints. MUST read SKILL.md BEFORE creating, moving, or restructuring any progress file.

0
installs
▌
Repo Scaffold · motiful bundle
Scaffold a new project workspace. Supports two archetypes: public open-source (split repos with independent skill distribution) and private monorepo (unified codebase with optional doc separation). Use when the user says "scaffold a project", "set up a workspace", or "create a new repo". Also called by skill-forge when creating a complex new skill that needs a full workspace with backstage.

0
installs
▌
Rules As Skills · motiful bundle
Rule-skill protocol — hard constraints delivered as dynamically-loaded skills with -rules suffix. MUST treat any skill named *-rules as MUST-level hard constraints (load-before-act, not advisory). When authoring new hard constraints, prefer rule-skill form over traditional rule files (unless universal-and-short). Existing -rules skills: raise loading priority, enforce strict compliance, proactively load when trigger scenarios match. Installation activates global protocol across Claude Code, Codex, Cursor, Windsurf, OpenClaw via scripts/install-meta-rule.sh — one meta-rule covers all -rules skills (current and future). Use when: writing MUST/NEVER boundaries for AI agents, evaluating whether a constraint should be a rule-skill, or modernizing legacy rule files. MUST read SKILL.md BEFORE creating any constraint skill.

0
installs
▌
Self Review · motiful bundle
Run a 4-pillar, 6-dimension alignment audit on the current project. Checks design currency, executes artifact verification, detects skill deposits. Use when the user says "self-review", "审视一下", or "audit". Report-only — never auto-fix.

0
installs
▌
Readme Craft · motiful bundle
Generate and improve README files using a 3-tier layout strategy, GitHub-native formatting patterns, badge guidance, and a state-driven workflow. Use when the user says "write a README", "generate a README", "create a README", "improve this README", "review my README", "make my README better", "add badges", or "fix my README layout".

0
installs
▌
Maintenance Rules · motiful
Maintenance rules for readme-craft. MUST keep quality checklist item count consistent across SKILL.md, README, and case study. MUST regenerate docs/ images when referenced content changes. MUST keep templates aligned with current methodology. MUST keep SKILL.md under 500 lines. Triggers on "update readme-craft", "maintain readme-craft", "check readme-craft consistency".

0
installs
▌
Skill Forge · motiful bundle
Validate, fix, and publish skills as GitHub repos. Structures workflow skills for execution fidelity. Registers skills across platforms via symlinks and guides first-use onboarding. Use when the user says "create a skill", "forge a skill", "review this skill repo", "audit this skill", "audit all my skills", "audit this project", "clean up my skills", "check my skill", "publish this skill", "push this to GitHub", "structure my workflow skill", "extract a skill from this folder", "turn my prototype into a skill", or points to a project directory with mixed skills and rules, or to an engineering folder where a skill was being prototyped. Forge: triage → discover → classify → validate → fix → local ready. Workshop input → triage extracts skill before audit. Nothing found → onboard user, scaffold, then same pipeline. Publish to GitHub when requested (Step 4).

0
installs
▌
Product Shots · motiful bundle
Front-door router for the product-shots ecosystem. Clarifies underspecified visual creation requests through a 4-stage state machine, injects platform visual DNA (Amazon + 7 social platforms) and industry visual DNA (7 industries), enforces a unified Negative Constraints prompt patch, then routes to one of five downstream business skills (product-shots-main-image / product-shots-detail-page / product-shots-multi-angle / product-shots-ad-creative / product-shots-social-post). Use when the user says "I need a product image", "design something for my listing", "I need content for Instagram", "make an ad for me", "make a cover image", "create a post", "做一个商品图", "帮我做个详情页", "帮我做个广告图", "做一个社媒图", "做一张图", "帮我设计", "做个封面" — i.e. any underspecified visual creation request that needs clarification before generation. This is the intent-routing hub of the product-shots ecosystem.

0
installs
▌
Product Shots Image Gen · motiful bundle
Unified image-generation engine for the product-shots ecosystem. Dispatches to the right model family (OpenAI gpt-image-2 / Gemini gemini-3-pro-image-preview Nano Banana Pro) with one parameterised script for text-to-image and image-to-image. Primary backend: OmniMaaS / Cloubic gateway (https://api.omnimaas.com/v1); also supports any OpenAI-SDK-compatible gateway via fallback env vars. Auto-resizes oversized reference images to prevent edge-proxy timeouts. Use when the user says "generate an image", "make a picture", "create a visual", "render this", "edit this image", "做一张图", "生成图片", "改这张图" — or when invoked as the image-generation backend by another product-shots skill (main-image / detail-page / ad-creative / social-post / multi-angle). NOT a creative-direction skill: takes a prompt + optional reference images, returns a file path.

0
installs
▌
Product Shots Main Image · motiful bundle
Designs Amazon-compliant main product images and the 7 secondary image types (Infographic / Multi-angle / Detail Shot / Lifestyle / Variants / What's in Box / Size Reference) — with platform-mandatory main-image rules, conversion-rate-tuned secondary types per product category, and multi-image consistency anchored to the main image URL. Use when the user says "Amazon main image", "亚马逊主图", "product main image", "white background product image", "Amazon listing image", "亚马逊副图", "secondary images", "product carousel images", or any request for the 1:1 product image suite that lives on the Amazon detail page carousel. For A+ Content / detail-page modules (21:9 Hero Banner and 3:2 module layouts), see the `product-shots-detail-page` skill.

0
installs
▌
Product Shots Ad Creative · motiful bundle
Designs high-performing ad creatives across Instagram, Facebook, TikTok, LinkedIn, Google (Display / Demand Gen), YouTube, Pinterest, and X/Twitter — locking platform dimensions, safe zones, text overlay policy, character limits, industry visual DNA, ad objective hierarchy, composition patterns, CTA strategy, and prompt sanitation. Use when the user says "create an ad", "design an ad creative", "make an ad", "广告创意", "帮我做个广告图", "Instagram ad", "TikTok ad", "Facebook ad", "Google Display ad", "LinkedIn ad", "YouTube ad", "Pinterest ad", "promotional image", "campaign creative", "ad banner", "投放图", or any platform-specific ad request. Routed from `product-shots` when `asset_type == "ad"` or `is_promotion == True`.

0
installs
▌
Product Shots Detail Page · motiful bundle
Designs Amazon A+ Content (formerly Enhanced Brand Content) — the 8 module suite that appears below the standard product carousel for Brand Registered sellers. Covers Hero Banner (21:9 / 2388×1024), Pain Points / Selling Points / Technology / Data / How-to-Use / Variants (3:2 / 1536×1024), and Endorsement (21:9), with mobile safe-area rule, 30pt text floor, and cross-module consistency anchored to the main image URL. Use when the user says "A+ page", "A+ content", "Amazon A+", "Brand Content", "Enhanced Brand Content", "亚马逊详情页", "A+ 详情页", "21:9 banner", "Hero Banner", "Amazon detail page module", or any request for the brand-registered detail-page module suite. For the 1:1 main image and carousel secondary images, see the `product-shots-main-image` skill.

0
installs
▌
Product Shots Multi Angle · motiful bundle
Generates 9 consistent multi-angle fashion-editorial portraits from a single reference image, with locked identity (face/skin/eyes), preserved hairstyle structure, faithful outfit/accessories, and a unified photography style across all frames. Use when the user says "multi-angle", "multi-angle shots", "九连拍", "多角度九连拍", "9-angle portraits", "fashion lookbook", "model consistency series", "consistent portraits from one photo", "generate 9 angles of this model", or "e-commerce model multi-angle pack". Part of the product-shots ecosystem for cross-border e-commerce apparel and accessory listings.

0
installs
▌
Product Shots Social Post · motiful bundle
Designs social-platform-native visuals (Feed, Story, Reel, Carousel formats) for Instagram, TikTok, Facebook, Pinterest, RedNote, LinkedIn, X/Twitter and other social platforms — with platform-correct dimensions, safe zones, industry visual DNA, engagement hooks, and cross-slide consistency. Use when the user says "social post", "Instagram post", "IG post", "TikTok post", "Facebook post", "Pinterest pin", "social carousel", "feed post", "story post", "make a post", "design a social visual", "社媒帖", "做一个社媒图", or any underspecified social-media visual request. Routed from `product-shots` for the organic-social branch (non-ad).

0
installs
▌
Ctx · motiful bundle
Sets up and orchestrates a ctx knowledge base — a lean, living single source of truth for multi-session AI-agent work — and classifies any doc or finding by its lifetime, routing the work to the right companion skill. Use when starting or scaffolding ctx on a new project, when unsure where a finding belongs (spec vs decision vs progress vs scratch), when unsure which ctx skill handles a task, or when docs have sprawled into redundant, contradictory piles that need converging. Entry point for the collection; routes to ctx-adopt (existing repos), ctx-merge (converge sources), ctx-spec (specs and ADRs), ctx-progress (work tracking), ctx-report (reports for a human), ctx-serve (host processes across sessions), ctx-compact (pre-reset checkpoint). For an existing/brownfield repo, use ctx-adopt instead.

0
installs
▌
Ctx Spec · motiful bundle
Writes specs, ADRs, architecture and design docs that an AI coding agent can build directly from — the right granularity (constraints, not hand-written implementation), testable EARS acceptance criteria, and ADR discipline (record only decided choices, supersede in place). Use when writing or restructuring a spec, a decision record (ADR), an architecture doc, or a design doc in a ctx knowledge base, or when deciding how detailed a spec needs to be.

0
installs
▌
Ctx Adopt · motiful
Bring an EXISTING project (brownfield) under ctx with minimal disruption. Decides where the /ctx folder lives (in-repo directory by default, or a gitignored symlink to an external sibling store named project-name-ctx when the context must not ship with public code), which pointer file announces it (respect the project's existing AGENTS.md/CLAUDE.md; else the running agent's native one), and ROUTES the actual doc-writing to the domain skills (ctx-merge / ctx-spec / ctx-progress / ctx-report) rather than writing shallow versions itself. Use when a user says "apply ctx to this existing repo / bring this repo under ctx", when deciding whether ctx must stay separable from published code, or when onboarding a messy existing repo.

0
installs
▌
Ctx Merge · motiful
Converges many scattered sources — dated research notes, subagent outputs, audit reports, revision cycles — into one living source of truth without silently dropping or distorting anything, routing each conclusion to exactly one home via a visible disposition ledger and surfacing conflicts as choices for a human. Use when merging or consolidating notes/reports into a ctx source of truth, integrating subagent research, synthesizing multiple audit reports, closing a decision cycle where alternatives existed, or rolling a corpus too large for one context through successive batches. Not for writing a single fresh doc from scratch — use ctx-spec.

0
installs
▌
Ctx Serve · motiful
Hosts a project's long-running processes — dev servers, watchers, build daemons — in tmux so they survive session exit and are shared across parallel agent sessions on one repo, recording their durable topology in a committed service manifest and detecting live status rather than storing it. Use when a task needs a dev server or watcher running, when parallel sessions must share one running service, when a process must outlive a /compact or session reset, or when reattaching to or restarting a service a prior session started. Records topology in ctx/services.md; a narrow operational companion in a ctx knowledge base. Not for one-shot foreground commands.

0
installs
▌
Ctx Report · motiful
Produces a disposable HTML report laid out for a human to read, comment on, and decide from — then distills the keep-worthy conclusions into the source of truth and archives the report. Use when writing a report, a review doc, or an options-for-a-decision document for a human to weigh in on in a ctx knowledge base, when a human has commented on a report and it needs distilling, or when un-merged reports are piling up. Not for converging a pile of raw notes or subagent outputs straight into the source of truth — use ctx-merge for that.

0
installs
▌
Ctx Compact · motiful
Sweeps everything decided in the current session into its correct source-of-truth home — progress, decisions, spec — and verifies the knowledge base is current and internally consistent before a context reset, so a /compact or a new session loses nothing. Use before running /compact, before ending a session, or whenever the user says they are about to reset or hand off and wants a safety checkpoint. A thin orchestrator over ctx-progress, ctx-merge, ctx-spec, and the consistency gate — it introduces no new rules, it runs the existing ones as a checklist. Not for routine mid-session saves — that is sink-same-turn in ctx-progress.

0
installs
▌
Ctx Progress · motiful
Tracks the WORK truth of a project — where we are, what's next, and what to read first — in a living progress file a fresh session can resume from, including cross-session handoff. Use when updating work or project state in a ctx knowledge base, recording what's done or what's next, opening a progress subtree as it grows past a flat file, handing off to a new session, or auditing a project for progress drift.

0
installs
▌
Booth · motiful bundle
Booth coordinates parallel Claude Code sessions (decks) through a daemon. Provides signal meanings, check flow, report format, and deck lifecycle context. Activates when booth signals (/booth-check, /booth-alert, /booth-beat) appear or when working in a booth-managed project.

0
installs
▌
Booth Dj · motiful
You are DJ — Booth's AI project manager. Dispatch work to decks, evaluate reports, deliver to user. Never write code yourself. Critical: resume unconditional, records persist, CLI first. Activates when BOOTH_ROLE=dj.

0
installs
▌
Booth Beat · motiful
Booth daemon beat signal. Periodic patrol for DJ: review deck states, process completed work, dispatch pending tasks, detect anomalies. Activates when daemon injects /booth-beat into the DJ session.

0
installs
▌
Booth Deck · motiful
You are a Booth Deck — execute tasks, self-verify on /booth-check, submit reports via `booth report`. NEVER run: booth stop, booth restart, booth shutdown. Activates when BOOTH_ROLE=deck or /booth-check received.

0
installs
▌
Booth Alert · motiful
Booth daemon alert signal. Notifies DJ of deck state changes: check complete (report ready), deck exited unexpectedly. Activates when daemon injects /booth-alert into the DJ session.

0
installs
▌
Booth Check · motiful
Booth daemon check signal. Triggers deck self-verification: review changes, fix issues, run tests, commit, and submit a report via `booth report`. Activates when daemon injects /booth-check into a deck session.

0
installs
▌
Triage Rules · motiful
Two-axis triage protocol for any AI agent. When facing a batch of findings, bug reports, audit results, or todo items — MUST sort by (confidence × blast-radius) before proposing actions. Confident + reversible/local damage = self-execute (Lane A). Confident + irreversible/colossal = recommend-and-ask (Lane B1). Uncertain regardless of risk = explain options and defer (Lane B2). Output as a scannable decision board, not a wall of text. Activates whenever an agent has just produced or received N≥2 findings/proposals/todos and is about to suggest actions. Also enforces a YAGNI self-check on items that introduce new mechanism, defensive code, future abstraction, or replace working systems.

0
installs
▌
Booth Dj Rules · motiful
Hard constraints for booth DJ when investigating bugs and dispatching fixes. MUST do design research before recording a bug or writing a fix prompt. MUST separate phenomenon from cause. NEVER dispatch a fix in the same turn the bug was reported. NEVER revert a previous fix without re-validating its original concern. NEVER let a fix prompt omit design intent. Activates when BOOTH_ROLE=dj and the user reports a bug, symptom, regression, or unexpected behavior.

0
installs
▌
Booth Compact Recovery · motiful
Booth daemon compaction recovery signal. Restores session context after CC context compaction. Tells DJ/deck their role and points to recovery files. Activates when daemon injects /booth-compact-recovery after compaction.

0
installs

34 published skills