Explore skills
Showing 15361–15390 of 77079 skills
Create visual moodboards from collected inspiration with iterative refinement. Use after trend research or website analysis to synthesize design direction before implementation.
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexResearch latest UI/UX trends from Dribbble and design communities. Use when starting a design project to understand current visual trends, color palettes, and layout patterns.
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexBrowse and select fonts from Google Fonts or curated pairings. Use to find the perfect typography for a design project.
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexSystematic debugging with persistent state across context resets
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexGather phase context through adaptive questioning before planning. Use --all to skip area selection and discuss all gray areas interactively. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexImport a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexBuild, query, and inspect the project knowledge graph in .planning/graphs/
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexQuery, inspect, or refresh codebase intelligence files in .planning/intel/
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexExecute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexResearch how to implement a phase (standalone - usually use /gsd:plan-phase instead)
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexSchedule a future resume of work - e.g. '/gsd:resume-at 09:00', '/gsd:resume-at +2h', or '/gsd:resume-at 04:00 --cmd /gsd:execute-phase 9'
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodexResume work from previous session with full context restoration
davepoon/buildwithclaude
Stars: 3.7kClaude CodeCodex抓取抖音单条视频的完整评论区(一级评论 + 全部楼中楼回复)和视频详情,可选下载视频,输出按点赞排序的「评论全文.md」和原始 JSON。在已登录抖音的真实浏览器里运行(Claude in Chrome,或 Grok Bot 等 Agent 自带、能执行页面脚本的浏览器),借页面自带 SDK 签名,不需要 TikHub、Playwright 或 a_bogus 逆向。用户给出抖音视频链接(douyin.com/video/…、带 modal_id 的主页链接、v.douyin.com 短链),并说"看评论区""抓评论""拉评论""评论区有什么质疑/疑问""参考评论区"时使用。只适用于抖音单条视频;小红书、B 站、批量采集博主全部作品不适用。
Pluviobyte/saas-growth-agents
Stars: 542Claude CodeCodex帮用户在自己的 Agent(Grok Bot、Muse、Dot、Hermes、OpenClaw 等)里装好 saas-growth-agents 的某个 Bot: 新词监控、出海站点运营、社媒分析,或附带的交易雷达。先问清需求,在本地用演练模式和免费的余额查询验证, 再生成一段定制好的安装消息让用户发给 Bot。用户说「帮我配一个出海运营 Bot」「帮我配一个 Grok Bot」「把交易雷达装到我的 Bot」 「生成发给 Bot 的安装话术」时使用。
Pluviobyte/saas-growth-agents
Stars: 542Claude CodeCodexConvene the Council of High Intelligence — multi-persona deliberation with historical thinkers for deeper analysis of complex problems.
0xNyk/council-of-high-intelligence
Stars: 4.8kClaude CodeCodexContent production in three modes: rewrite, Xiaohongshu (小红书) image post, short video. Rewrite (default): turns an AI-sounding Chinese or mixed Chinese-English draft (post, newsletter, engineering blog, commentary) into the author's restrained style: few emoji, short paragraphs, hedged claims, neutral wording, English terms split by spaces. Triggers: 按我的风格改, 去 AI 味, 润色, 改改这篇, or a vague 帮我改改 when the context is a structured draft. Also for a Xiaohongshu image post from scratch (title, cover, cards, body, hooks); read references/xhs-post.md first. Also turns a document, research, notes or an article into a 60-180 s vertical video (抖音, 小红书, 视频号, B站: real sources, voice-over, captions, cover). Triggers: 做成视频, 做个短视频, 剪个 90 秒版本, 配音, 换成我的声音, or complaints of 字太密, AI 味太重, 容易走神; read references/video-pipeline.md first.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexDraft or check a pull request description in a fixed format (background, changes, behavior changes, out of scope, verification, rollback, not done, related) for GitHub or GitLab. Use when opening a PR, when the MCode Review summary reports missing description sections, or when the user asks for a PR description.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexThe weekly self-tuning loop for the MCode Review bot on GitHub or GitLab. Measures the bot on a repository's recent PRs (threads per PR, which kinds people answer or dismiss, what was unanswered at merge, cost per round, time to merge, follow-up fixes), finds noise and misses, proposes at most three rule changes with their expected effect on each goal, backtests them on past PRs with known outcomes within an agreed token budget, has an independent check recompute the numbers, and changes rules only after a person approves. The first run only measures. Use for requests to run pr-review-tuning or to measure or tune the review bot, for the weekly scheduled run, and for settling a proposal (approve or reject P1).
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodex为已排期的需求做方案:列至少两个选项、写决策记录、评估波及面(blast radius)、定验收检查点,全部落进需求文档。Use when a requirement is scheduled and before implementation, or when someone asks 方案怎么定 / 这个改动会影响哪些地方.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodex在需求刚提出时,先挑战它是否该做,写下一条能验证的预期效果,再用模板建飞书需求文档和飞书项目(Meegle)工作项,两边互相链接。Use when someone raises a product or technical requirement, says 提需求 / 我想要 / 能不能加, or before any requirement work starts without a doc and a work item.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodex对一个已受理的需求,对照当前在做的工作(WIP)评估成本、影响、风险,给出排期建议和理由;提出人提建议,负责人拍板。Use after req-intake, at backlog grooming or sprint planning, or when someone asks 这个需求优先级多高 / 能不能插队.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodex上线前做就绪检查(回滚方案、可观测性、完成定义 DoD),全部有证据后再推进 Meegle 状态或节点。Use before a requirement is deployed or marked done, when someone says 可以上线了吗 / 准备发布, or before transitioning the work item to a released state.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodex按固定节奏跟进进行中的需求,用站会格式记录进展、阻塞和下一步;超过约定时间没有更新的需求要显式标出来,不能悄悄沉下去。Use for daily or weekly requirement check-ins, when asked 这个需求到哪了 / 有没有卡住的, or from a scheduled routine.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexWrite the brief before handing a non-trivial task to an agent or subagent, covering stakes, your own hypothesis, goal and scope in your words, what "verified" will mean, and whether the agent is thinking with you or for you. Use before starting a MiniMax Code session, spawning a subagent, or delegating a PR, analysis or doc.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexUse when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change description", or "make this PR/CL description easier to review". DO NOT TRIGGER for code review, PR splitting, code restructuring, user-facing changelogs, or reviewer replies unless the requested output is a change description.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexUse when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code health, design, functionality, tests, maintainability, specialist risk, or approval risk. TRIGGER on "review this PR", "code review", "LGTM?", "approve?", "is this code/diff/change safe to merge/deploy?", and local diff reviews. DO NOT TRIGGER for PR descriptions, PR splitting, author review-feedback responses, or non-code safety questions unless code review is requested.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexUse when a code hotfix, rollback alternative, production/security/legal fix, launch blocker, or hard external deadline claims expedited review or relaxed process. TRIGGER on "emergency change", "hotfix", "prod incident", "major security hole", "must ship today", "hard deadline", "bypass review", or "fast-track this PR" for qualification only. DO NOT TRIGGER for ordinary urgency, soft deadlines, Friday timing, manager pressure, time-zone delay, or review unless emergency status is disputed.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexUse when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I phrase this review comment?", "write review comments", author pushback, or turning findings into PR comments. If role is unclear, ask reviewer or author. DO NOT TRIGGER for full code review, PR descriptions, or author responses unless wording is requested.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexUse when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates. TRIGGER on "address review feedback", "respond to this review comment", "reviewer asked", "I disagree with reviewer", "what should I reply?", or "apply PR comments". If role is unclear, ask reviewer or author. DO NOT TRIGGER for reviewer comment writing, full code review, or PR descriptions unless author-response behavior is requested.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodexUse when planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests into small reviewable PRs or CLs. TRIGGER on "split this PR", "this diff is too large", "stacked PRs", "change sequence", "reviewable chunks", "migration plan", "how should I break this up?", or implementation scope too broad for one review. DO NOT TRIGGER for full code review, PR description writing, or tiny one-file edits that already form one self-contained change.
MiniMax-AI/mcode-stack
Stars: 726Claude CodeCodex