Write or review UI copy — buttons, errors, empty states, microcopy, notifications, labels — using the voice & tone system (clear, concise, useful, human, honest) with the what→why→how error formula and inclusive-language rules. Use when the user needs interface copy, error messages, empty-state text, or a copy review.
日本語の概要は準備中です。原文の説明を表示しています。
plugin87/ux-ui-agent-skills☆ 2,0782026年10月11日 更新
Runs the production schedule — sequencing and releasing work, managing work in process and changeovers, and holding the promised date when the floor and the order book disagree. Use this to build or fix a production schedule, decide what to run next, diagnose why lead times are growing while machines look busy, set up OEE or throughput measurement, or choose between make-to-stock and make-to-order for a product line.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Manages the relationship with a represented workforce — administering a collective agreement, handling grievances, understanding what supervisors may and may not say, and preparing for bargaining. Use this for a grievance or arbitration question, a work rule change in a represented unit, supervisor guidance during organizing, contract interpretation and past practice, or preparation for negotiations.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and the controls that actually address the realistic threats. Use this when designing a feature or system, when a change touches authentication, data handling, payments, or external input, before a security review, or when deciding which security work is worth doing at all.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking, and patch policy. Use this to stand up or fix a vulnerability program, triage scanner output, decide what to fix first, set patch SLAs, handle a disclosure from an outside researcher, or report posture to leadership.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a system, decide which automation to build first, or audit an automation that is not delivering.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Builds questions and assessments that measure what they claim — matching item type to the thing being assessed, writing distractors that diagnose, and telling a question that measures learning from one that measures reading speed or test-taking. Use this to write or review assessment items, design a unit check or diagnostic, work out why scores do not match classroom performance, or decide how much evidence a claim about mastery actually needs.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Judges whether material for children under six is developmentally plausible — what is typical at each age, why pre-K is not a thinner kindergarten, and which frameworks apply where Common Core does not. Use this to design or review pre-K material, decide whether a task is reasonable for an age, choose the right framework for a pre-K alignment claim, or push back on material that pushes school-age expectations downward.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Aligns learning material to the standard it claims — choosing the right framework for the grade and subject, citing standards by code rather than reproducing their text, and telling a real alignment from a decorative one. Use this to align a worksheet, lesson or workbook to Common Core, NGSS or a state framework, to check an alignment claim before publishing, or to decide what may lawfully be printed on the cover.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Runs environment, health and safety on an operating site — hazard controls in order of effectiveness, incident recording and reporting obligations, and safety measurement that does not reward silence. Use this to build or audit a safety program, decide what controls a hazard actually needs, work out whether an injury is recordable or reportable, investigate an incident, or fix safety metrics that have stopped producing reports.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Keeps production assets available — ranking equipment by consequence of failure, setting preventive and predictive intervals, sizing spares, and moving a plant off reactive maintenance. Use this to build or fix a maintenance program, decide what to put on a PM schedule, diagnose repeat failures on one asset, justify spares inventory, or work out why a plant that maintains everything still has unplanned downtime.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited, find out why a plan keeps slipping, work out what a date change actually costs, or judge whether a reported percentage complete means anything.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. Use this to plan a rollout, recover an implementation nobody is using, handle resistance to a change, sequence communications, or work out why a technically successful project changed nothing.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three times in slightly different forms, or when a token or component needs adding without breaking what exists.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a contractor arrangement, respond to an accommodation request, work out what records to keep and for how long, or sanity-check a practice you inherited.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Designs quotas, territories and commission plans that produce the behavior the business needs — sizing territories against real potential, setting quotas people can hit often enough to believe in, choosing what to pay on, handling accelerators, draws, clawbacks and disputes, and changing a plan without destroying trust. Use this to build or fix a comp plan, allocate territories, work out why reps are chasing the wrong deals, or plan a mid-year change.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新
Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control. Use this to build a referral or affiliate program, diagnose one that is not producing, decide what incentive to offer, or judge whether referral is a realistic channel for a product.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0672026年9月18日 更新