3.1万 件 ・ 関連度順
概要と使いどころ
This skill should be used when the user asks to "优化简历", "resume optimization", "简历诊断", "tailor resume to JD", "改简历", "resume review", "简历优化助手", or when the user mentions "校招", "社招", "ATS", "JD匹配", "Word批注", shares a .docx resume path alongside a job description, or wants to match their resume to a specific job posting. Also triggers on "resume expert", "HR feedback", "interview prep with resume".
日本語の概要は準備中です。原文の説明を表示しています。
Discuss a community-edition product requirement with the user, draft a bilingual (Chinese + English) PRD for review, then — after explicit user approval — create the English-only issue on GitHub (<OWNER/REPO>). Use whenever the user wants to turn a requirement (from a Feishu doc, a meeting note, a customer ask, or a rough idea) into a GitHub issue. Triggers on phrases like "create requirement doc", "create a requirement", "put this requirement on GitHub", "create new feature issue", "draft an issue for...", or anytime the user describes a product feature/improvement they want tracked. The format is opinionated (Background / Goal / Spec / Verification / Related, NO implementation details, draft shown bilingually for human review, issue itself written in English only).
日本語の概要は準備中です。原文の説明を表示しています。
A clear description of what this skill does and when to use it. Include specific trigger phrases like "do X" or "help me with Y". Also include negative triggers — "do NOT use when..." — to prevent false activations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting a bug or defect ticket, reviewing one someone else wrote, or deciding whether a reported problem is ready to file. Keeps what the reporter actually saw separate from what the agent later found out, so a reader can tell which lines are testimony and which are collected proof. Trigger phrases: 'file a bug', 'write up this defect', 'triage this report', 'is this ticket ready to file', 'what did the reporter actually see'.
日本語の概要は準備中です。原文の説明を表示しています。
VibeFarsi 63 motion patterns: production-level individual recipes and semantic parity. Use when implementing, reviewing or testing vibefarsi 63 motion patterns for React, Vite, Next.js or Perfect_AI projects.
日本語の概要は準備中です。原文の説明を表示しています。
VibeFarsi component integration: production-level official CLI, compound states, RTL. Use when implementing, reviewing or testing vibefarsi component integration for React, Vite, Next.js or Perfect_AI projects.
日本語の概要は準備中です。原文の説明を表示しています。
GLSL shader systems: production-level uniforms, color space, derivatives, precision. Use when implementing, reviewing or testing glsl shader systems for React, Vite, Next.js or Perfect_AI projects.
日本語の概要は準備中です。原文の説明を表示しています。
Easing mathematics: production-level cubic bezier, damped spring, velocity continuity. Use when implementing, reviewing or testing easing mathematics for React, Vite, Next.js or Perfect_AI projects.
日本語の概要は準備中です。原文の説明を表示しています。
WAAPI and compositing: production-level GPU-friendly transform/opacity, offscreen pausing. Use when implementing, reviewing or testing waapi and compositing for React, Vite, Next.js or Perfect_AI projects.
日本語の概要は準備中です。原文の説明を表示しています。
Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deploying this teleprompt app with get-convex/static-hosting, especially when the user says /deploydev, /deployprod, deploy dev, deploy prod, deploy production, upload static hosting, or asks which Convex static-hosting command to run. Keeps dev uploads on fearless-dolphin-422 and production uploads on befitting-dodo-95.
日本語の概要は準備中です。原文の説明を表示しています。
Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.
日本語の概要は準備中です。原文の説明を表示しています。
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
日本語の概要は準備中です。原文の説明を表示しています。
Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
日本語の概要は準備中です。原文の説明を表示しています。
Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.
日本語の概要は準備中です。原文の説明を表示しています。
Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.
日本語の概要は準備中です。原文の説明を表示しています。
Routes general Convex requests to the right project skill. Use when the user asks which Convex skill to use or gives an underspecified Convex app task.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding WHERE to do work on Syntropic137 itself - "run this through Syntropic", "dispatch a workflow", "should this go in a workspace or local", "kick off a run on the Mini", "dogfood this", "build Syntropic inside Syntropic", "why did the agent's push fail", "can an agent run our QA", "the execution says completed but nothing shipped". Covers what a workspace agent can and cannot do, why `.github/workflows` pushes must come from the local machine, how to write a task prompt that does not repeat a known failure, and how to verify a run actually delivered. Do NOT use for PR/release mechanics (see `devops`), for using the `syn` CLI as an end user (see the syntropic137 plugin skills), or for authoring workflow YAML.
日本語の概要は準備中です。原文の説明を表示しています。
Use when turning something that happened into something that makes the next run better - "write a retro", "record this paper cut", "this bug escaped verification", "make this an eval", "why do we keep hitting this", "did that change actually help", "scorecard", "what did we learn from that run", "lessons keep getting re-learned". Covers the six-step loop (capture, classify, convert, change, measure, retro), the repo artifact each step produces, and how escaped bugs become eval cases. Do NOT use to design or judge a single workflow experiment (see `workflow-experimentation`, which this loop feeds), to decide where to run work (see `dogfooding`), or to debug one failed execution in the moment.
日本語の概要は準備中です。原文の説明を表示しています。
House conventions for this repository - commit message shape, branch naming, and where documents live. Use when writing a commit, opening a PR, or deciding where a new document belongs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building or changing Skyline UI (apps/syn-ui, packages/syn-ui/*) from a design - "build this screen from the board", "implement the design", "match the canvas", "new board landed", "build the Eval trend panel", "port this screen to Skyline", "does this match the design", "update the Shipped table", "snapshot the boards". Covers reading a `*.dc.html` board and the Skyline spec, building from them, comparing 1440px and 390px screenshots against the board, and recording the shipped screen. Do NOT use for small tweaks to a screen that has already shipped (change the code directly, no board needed), for the frozen React app apps/syn-dashboard-ui (never edit it), or for refreshing the CI screenshot baselines alone (see design/README.md).
日本語の概要は準備中です。原文の説明を表示しています。
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.
日本語の概要は準備中です。原文の説明を表示しています。
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for hyperparameter selection — learning rate formulas, LoRA rank, batch size, group size, schedules, and model-specific tuning. Use when the user asks about learning rate, batch size, hyperparameter tuning, or how to configure training parameters.
日本語の概要は準備中です。原文の説明を表示しています。