2,779 件 ・ 関連度順
概要と使いどころ
HR business partnership across talent strategy, org development, and employee relations. Use when building workforce plans, designing performance reviews, resolving employee relations cases, or advising leadership on org change.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and repair an internal knowledge base — staleness, ownership gaps, orphans, duplication, and findability. Use when the wiki is untrusted, docs are out of date, nobody owns pages, or search returns the wrong answer.
日本語の概要は準備中です。原文の説明を表示しています。
Edit mathematically, empirically, or technically dense papers for readers outside the author’s specialty, including empirical legal scholarship, law-and-economics models, and legal-technology research. Clarifies terminology, antecedents, study design, and claim–statistic relationships while checking equations, numbers, quotations, and citations against the source. Use to clarify exposition or de-jargonize a technical draft; not to rewrite briefs or doctrinal arguments. Produces an edited draft and audit memo. Full integrity checks and original-format rendering require suitable extraction, code execution, and document tools; otherwise provides proposed edits with verification limits disclosed.
日本語の概要は準備中です。原文の説明を表示しています。
Invoice review, non-compliance flagging, rejection communication, billing trend analysis, and conversation preparation for in-house legal ops teams managing outside counsel. Review invoices against billing guidelines; flag block billing, prohibited fees, rate violations, staffing violations, late submission. Produce line-item review report and approval note. Draft rejection letter to outside counsel. Build invoice review checklist. Analyse billing trends across multiple invoices and produce a structured conversation guide for the relationship review. Identify systemic patterns and produce formal non-compliance notice. Trigger on: 'review this invoice', 'flag billing issues', 'check invoice against guidelines', 'write the rejection letter', 'build an invoice checklist', 'block billing', 'UTBMS', 'billing non-compliance', 'analyse our invoices', 'billing trends', 'prep for the billing conversation', 'relationship review', 'the firm keeps doing this', 'escalate'.
日本語の概要は準備中です。原文の説明を表示しています。
Map a complex topic by placing factors on hexagonal tiles where adjacency signals a claimed relationship. Use when students need to surface hidden connections in a system before analysis or action.
日本語の概要は準備中です。原文の説明を表示しています。
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything else. Kills the "looks shipped, isn't shipped" bug across sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Build and execute brand marketing strategy for B2B companies — thought leadership, ABM brand layer, trust signals, LinkedIn presence, long sales cycle brand touchpoints, and enterprise credibility. Use when the user says "B2B marketing", "B2B brand", "business to business marketing", "selling to companies", "enterprise marketing", "we sell to businesses", "B2B brand strategy", "thought leadership strategy", "B2B content marketing", "account-based marketing brand", "B2B positioning", "how do we build trust with buyers", or is marketing a product or service sold to other businesses rather than consumers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a PERSONAL brand needs to make money — three funnel versions for founder, coach, and creator, an offer ladder from free to low to mid to high ticket, pricing psychology, inbound versus outbound outreach, and brand deal and sponsorship negotiation, with tax and legal variants for US LLC, EU per country, SEA Pte Ltd, and LATAM MEI. Trigger on 'monetize my personal brand', 'offer ladder', 'launch my course', 'coaching packages', 'sponsorship rates', 'I have an audience and no income'. Not for — a company product offer, see `31-offer-design-global` and `17-pricing-strategy-global`; the strategy that comes first, see `23-personal-brand-strategy-global`; running the community, see `28-community-building-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi mot CA NHAN can viet BAI DAI de xay uy tin, khong phai copy ban hang — 3 cau truc chuan cho thi truong VN gom PAS-Insight cho founder, Story-Lesson-CTA cho coach, Hook-List-Reveal cho creator; 6 cong thuc hook long-form; ky thuat nhip cau; do dai theo nen tang LinkedIn, Facebook, newsletter; ma tran tai su dung 1:5. Kich hoat khi user nhac 'viet bai LinkedIn', 'thought leadership', 'long form post', 'newsletter ca nhan', 'viet bai chuyen sau', 'khong biet viet gi tren trang ca nhan', 'muon duoc coi la chuyen gia'. Khong dung cho — copy quang cao tra tien thi dung skill 05-copy-quang-cao; caption ngan cho fanpage doanh nghiep thi dung skill 37-caption-social; kich ban video ngan thi dung skill 04-script-video.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a PERSONAL brand needs long-form WRITTEN content that builds authority rather than sells — LinkedIn posts, X threads, Substack and Medium essays, using PAS-Insight for founders, Story-Lesson-CTA for coaches, and Hook-List-Reveal for creators, with six hook formulas and a 1-to-5 repurpose. Trigger on 'LinkedIn post', 'thought leadership', 'write a Twitter thread', 'newsletter essay', 'Substack post', 'I want to be known for this topic'. Also use when the user has an opinion and wants it turned into a post. Not for — company brand captions, see `37-social-caption-global`; paid ad copy, see `05-ad-copy-global`; short video scripts, see `04-script-video-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a price has to be set or changed — value-based pricing, anchoring, charm pricing, decoy tiers, good-better-best packaging, discount policy, and margin math, with currency psychology for US, EU, SEA, and LATAM plus dropshipping markup and BE-ROAS. Trigger on 'pricing strategy', 'how much should I charge', 'should I raise prices', 'price tiers', 'customers say it is too expensive', 'dropshipping markup'. Also use when the product is not selling and the user suspects price is the reason. Not for — bonuses, guarantee, and value stack around the price, see `31-offer-design-global`; persuasion beyond price, see `16-marketing-psychology-global`; ad budget math, see `10-reverse-kpi-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use after /gsd-verify-work passes, when the work should become a PR. Pushes the branch, creates the PR with an auto-generated body, optionally triggers review, and tracks the merge, closing the plan-execute-verify-ship loop.
日本語の概要は準備中です。原文の説明を表示しています。
Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends. USE FOR: stylelint.config.*, .stylelintrc*, CSS or SCSS assets; CSS linting; duplicate style cleanup and naming-convention checks. DO NOT USE FOR: JavaScript or TypeScript lint ownership; runtime accessibility, performance, SEO, or header checks. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
Use webhint in .NET repositories that ship browser-facing frontends. Use when a repo needs CLI audits for accessibility, performance, security headers, PWA signals, SEO, or runtime page quality against a. USE FOR: the repo ships a browser-facing site and the user asks about accessibility, performance, SEO, security headers, or page quality; the repo has .hintrc, hint scripts, or a. DO NOT USE FOR: JavaScript or TypeScript semantic linting; route that to eslint or biome; stylesheet-only linting; route that to stylelint. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets. USE FOR: the repo has package.json, eslint.config.*, .eslintrc*, tsconfig.json, or JS/TS/React frontend files; the user asks for JavaScript or TypeScript linting, React rule. DO NOT USE FOR: CSS ownership by itself; route that to stylelint; HTML-only checks on static output; route that to htmlhint. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
Close out a change without the deep review loop: stage, simplify code and docs, run the project's checks, smoke test, update the changelog, self-improve, and ship. Use when the user asks to "quick finalize", "quickly finalize", "finalize quickly", "light finalize", "wrap this up quickly", "close this out without the full review", or "ship this without the deep pass".
日本語の概要は準備中です。原文の説明を表示しています。
Designs convex/schema.ts tables, validators, indexes, and relationships, and keeps the schema honest as data evolves. Use when creating tables, adding fields, choosing index fields, modeling relationships, or when a validator error appears at deploy time.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive toolkit for creating, analyzing, and visualizing complex networks and graphs in Python. Use when working with network/graph data structures, analyzing relationships between entities, computing graph algorithms (shortest paths, centrality, clustering), detecting communities, generating synthetic networks, or visualizing network topologies. Applicable to social networks, biological networks, transportation systems, citation networks, and any domain involving pairwise relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-ship gate — runs detector, verifies brief and tokens, applies the 10-pass finish bar, ranks findings by feedback hierarchy. Use when the user wants to ship, merge, or finalize a surface and needs a verdict (READY / NOT READY / BLOCKED) before committing. Invoke when the user asks for finalize on their UI, or mentions 'finalize' alongside design / UI / frontend work.
日本語の概要は準備中です。原文の説明を表示しています。
Look up NYC ACRIS deeds, mortgages, liens, sales, and ownership history. Use for property transactions or recorded ownership; not permits or violations.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to build personal brand, thought leadership, or IP as a founder on Twitter/X or LinkedIn. Also use when the user mentions "founder brand", "personal content", "build audience", or "grow my following".
日本語の概要は準備中です。原文の説明を表示しています。
Audits Rust code for unsafe blocks, ownership issues, and Cargo dependency risks. Use when reviewing Rust code or before merging Rust changes.
日本語の概要は準備中です。原文の説明を表示しています。
Personal CRM and contact management - manage contacts, relationships, and interactions. Use when the user discusses contacts, people, or relationship tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Reconstruct and report long-running or multi-turn research, architecture questions, reviews, decisions, completion results, and status as a clear, self-contained brief. Use when a reader must re-enter earlier context, understand the real question and its relationships, distinguish verified facts from judgment and open evidence, or make a decision without reconstructing the work log. Quote the relevant original user wording before substantive analysis, keep one coherent main line, use spatial diagrams when relationships matter, and finish with an explicit decision boundary and practical next step.
日本語の概要は準備中です。原文の説明を表示しています。