Skills on AI

Do more faster with your AI

A catalog of AI coding skills — reference material an AI agent loads on demand for testing frameworks, cloud platforms, databases, design systems, programming languages, and more. Each skill is a single SKILL.md file with trigger conditions and grounded content.

Filter skills

Accessibility & inclusion 6

ARIA Attributes — Use when asked to add or review ARIA (Accessible Rich Internet Applications) attributes — roles, states, and properties for dynamic/interactive elements — as a supplement to semantic HTML, not a replacement for it, and grounded in web-content-accessibility-guidelines' operable/perceivable criteria.
Cross Cultural Communication — Use when asked to communicate effectively across cultural backgrounds — cultural awareness, language differences, nonverbal communication, direct/indirect and high/low-context styles, sensitivity and adaptation — as a communication discipline, distinct from inclusive-language's specific wording focus.
Digital Inclusion — Use when asked about ensuring all individuals and communities can access and effectively use digital technologies — connectivity, digital skills/literacy, accessibility, culturally appropriate content, digital citizenship and safety — as the broad societal umbrella that accessibility-testing and web-content-accessibility-guidelines address one dimension of.
Keyboard Shortcut — Use when asked to design or document keyboard shortcuts (hotkeys) — accelerating workflow, accessibility for mobility-impaired users, consistency/standardization, customization — for a software application or operating system.
Screen Reader — Use when asked about how screen readers work and how to design/build for them — audio representation of content, semantic markup and alt text, navigation mechanisms, structural/context cues — as the underlying assistive technology screen-reader-testing verifies against.
Web Content Accessibility Guidelines — Use when asked about WCAG specifically — the perceivable/operable/understandable/robust (POUR) principles and A/AA/AAA conformance levels — as the formal standard accessibility-testing and screen-reader-testing verify compliance against.

Business analysis 6

Demand Analysis — Use when asked to run or explain a demand analysis — estimating and understanding customer demand for a product or service (market size, price sensitivity, demand drivers) — as the market-feasibility input to a broader feasibility-analysis or business case.
Feasibility Analysis — Use when asked to run or explain a feasibility analysis — assessing whether a proposed project, product, or venture is practically achievable across technical, financial, operational, legal, and market dimensions — before committing significant resources to it.
Five Forces Analysis — Use when asked to run or explain a Porter's Five Forces analysis — assessing industry competitiveness via rivalry, supplier/buyer power, and threats of new entrants/substitutes — as an industry-structure framework complementary to swot-analysis and pestle-analysis.
PESTLE Analysis — Use when asked to run or explain a PESTLE (or PEST) analysis — the macro-environmental factors framework for strategic planning — sourced from Wikipedia's PEST analysis article, including its PESTEL/STEEPLE variants and known limitations.
Stakeholder Analysis — Use when asked to run or explain a stakeholder analysis — identifying stakeholders and mapping their interest and influence (a power/interest grid) to plan engagement — as the analytical step that typically precedes formalizing responsibilities in a responsibility-assignment-matrix.
SWOT Analysis — Use when asked to run or explain a SWOT analysis — Strengths, Weaknesses, Opportunities, Threats — the internal-vs-external strategic planning framework, sourced from Wikipedia's SWOT analysis article, including its history and known limitations.

Business functions 22

Angel Investor — Use when asked about angel investors — high-net-worth individuals investing their own money in early-stage startups, typically before venture-capital involvement — as a distinct, usually smaller and more personally-involved funding source.
Board Deck — Use when asked to build or review a board deck — a presentation for a company's board of directors summarizing performance, risks, and decisions needed — distinct from an [[investor-update]], which is a lighter, more frequent written update rather than a governance-meeting presentation.
Branding — Use when asked to develop or apply a brand — brand identity, brand strategy, brand guidelines, consistency across touchpoints — as distinct from a single campaign or the broader marketing-manager function, which branding underlies and constrains.
Business Development — Use when asked about business development — market analysis, strategic partnerships, lead generation, relationship management, and expansion activities that grow a company's market position — as the broader function that joint-venture, spinoff, and spinout structures often serve.
Business Model Canvas — Use when asked to build or explain a Business Model Canvas — a one-page, nine-block visual template covering value proposition, customer segments, channels, revenue, cost structure, and more — as a structured way to design or communicate a business model before or alongside a full business plan.
Business Model Innovation — Use when asked about business model innovation — deliberately rethinking how a company creates, delivers, and captures value (not just its products) — as distinct from product innovation, and often expressed using the business-model-canvas as a working tool.
Communications Manager — Use when asked about the internal/organizational communications function — leadership messaging, change communications, or an internal communications plan — as distinct from public relations (see public-relations-manager), which targets external audiences, and general team communication norms (see ways-of-working).
Crisis Communication Plan — Use when asked to write a crisis communication plan — how an organization communicates externally, to media, customers, or the public, during a crisis — as distinct from an [[incident-response-plan]], which covers the internal operational or technical response rather than the external-facing message.
Finance Manager — Use when asked about the finance management function — budgeting/forecasting, financial statements (P&L, balance sheet, cash flow), unit economics, or a business case's financial justification — as an organizational function, not as personal financial or investment advice.
Information Manager — Use when asked about the information management function — information governance, data classification/retention, records management, or information security policy at the organizational level — as distinct from a technical database or security-tooling skill, which this function relies on but doesn't itself specify.
Investor Update — Use when asked to write a regular investor update — a concise, often-monthly written update on company progress sent to investors — distinct from a full [[board-deck]], which is prepared for a formal governance meeting rather than a lighter, more frequent written note.
Joint Venture — Use when asked about a joint venture (JV) — two or more independent entities forming a new, separate entity to pursue a shared business objective — as distinct from a general strategic partnership, and from spinoff/spinout, which separate a piece of one company rather than combine two.
Legal Manager — Use when asked about the in-house legal/general counsel function — contract review, corporate compliance, IP protection, or risk/liability management — as an organizational function, not as a substitute for actual legal advice from a qualified lawyer for a specific real situation or jurisdiction.
Market Expansion — Use when asked about market expansion — growing a business by entering new geographic markets or customer segments with an existing offering — as distinct from product-line-extension, which grows by adding new offerings to an existing market.
Marketing Manager — Use when asked about the marketing management function — brand positioning, the marketing mix, campaign planning, or marketing metrics (CAC, LTV, funnel conversion) — as distinct from sales management (see sales-manager) or public relations (see public-relations-manager), which marketing coordinates closely with but is not the same function as.
Operations Manager — Use when asked about the operations management function — process design/improvement, capacity planning, SLAs and service quality, or vendor/supplier management — as distinct from project management (see project-management), which manages bounded work rather than ongoing operational delivery.
Product Line Extension — Use when asked about product line extension — growing a business by adding new products/variants for an existing customer base — as distinct from market-expansion, which grows by reaching new markets with an existing offering.
Public Relations Manager — Use when asked about the public relations (PR) function — media relations, a press release, crisis/reputation management, or stakeholder communications strategy — as distinct from marketing (see marketing-manager) or internal communications (see communications-manager), which PR coordinates closely with but is not the same function as.
Sales Manager — Use when asked about the sales management function — pipeline/funnel management, sales methodologies (BANT, MEDDIC, SPIN), quota/forecast management, or CRM discipline — as distinct from marketing (see marketing-manager), which generates and qualifies demand that sales then converts.
Spinoff — Use when asked about a corporate spinoff — a parent company creating a new independent company by selling or distributing some of its assets or operations — as distinct from spinout (employee-initiated) and joint-venture (combining rather than separating entities).
Spinout — Use when asked about a spinout (employee spinout) — employees taking a technology or product and developing it into a new independent company — as distinct from spinoff (parent-initiated corporate restructuring).
Venture Capital — Use when asked about venture capital (VC) — how VC funding works, funding stages, what VCs look for, and the trade-offs of taking VC money — as a specific, larger-scale, professionally managed funding source distinct from angel-investor funding.

Business › Strategy & planning frameworks 17

Big Hairy Audacious Goal — Use when asked to write a BHAG (Big Hairy Audacious Goal) — a long-horizon, ambitious statement of ultimate organizational purpose — as distinct from a nearer-term, directly trackable North Star metric (see north-star) that operationalizes progress toward it.
Critical Success Factors — Use when asked to identify Critical Success Factors (CSFs) — the few essential areas an organization must excel at to achieve its mission — as the qualitative, area-of-focus counterpart to key-performance-indicators's quantitative metrics, and a direct input to strategic-balanced-scorecard.
Emergent Task Planning — Use when asked to apply Emergent Task Planning (ETP) — Francis Seah's just-in-time, flexible-goal productivity framework for unpredictable environments — as distinct from a fixed, upfront-planned approach like a yearly-planning-meeting's annual cycle or a rigid work-breakdown-structure.
Guide Star — Use when asked about a "guiding star" objective — the single overarching goal orienting a team or organization's decisions — the same underlying concept as a North Star metric (see north-star), under an alternate name some teams and frameworks use.
Key Performance Indicators — Use when asked to define, choose, or improve a Key Performance Indicator (KPI) — leading vs lagging indicators, measure vs metric, or how to check whether a proposed KPI is actually good — grounded in joelparkerhenderson/key-performance-indicator, as distinct from OKRs (see objectives-and-key-results).
Key Risk Indicators — Use when asked to define or choose a Key Risk Indicator (KRI) — an early-warning metric for organizational risk — as the risk-focused counterpart to key-performance-indicators's performance-focused metrics, typically used together for a full view of health.
Maturity Models — Use when asked to design, apply, or explain a maturity model — level naming conventions, top-down vs bottom-up construction, or well-known examples (CMMI, DevOps, Agile maturity models) — grounded in joelparkerhenderson/maturity-models, including documented rebuttals.
North Star — Use when asked to define a North Star metric or objective — the single overarching goal guiding a company's strategy and decisions — as distinct from a Big Hairy Audacious Goal (see big-hairy-audacious-goal), which is longer-horizon and more aspirational than a trackable North Star metric.
Objectives and Key Results — Use when asked to write OKRs (Objectives and Key Results) — an inspirational, team-actionable objective paired with measurable key results — grounded in joelparkerhenderson/objectives-and-key-results, including known real-world pros/cons, as distinct from KPIs alone (see key-performance-indicators).
Pitch Deck — Use when asked to write, structure, or critique a startup pitch deck — fundraising slideshow content, common templates, or investor-advice frameworks (market-first, asymmetric bets, aggregation theory) — grounded in joelparkerhenderson/pitch-deck.
Plan Do Check Act — Use when asked to explain or apply the PDCA (Plan-Do-Check-Act) improvement cycle, its PDSA (Plan-Do-Study-Act) variant, or how it compares to other iterative-improvement cycles (OODA, DMAIC) — sourced from Wikipedia's PDCA article.
SMART Criteria — Use when asked to write or check a goal/objective/task against SMART criteria (Specific, Measurable, Actionable, Relatable, Timely) or its SMARTER/FAST extensions — grounded in joelparkerhenderson/smart-criteria, as a quality check that pairs with OKRs (see objectives-and-key-results) and KPIs (see key-performance-indicators).
Strategic Balanced Scorecard — Use when asked to build a strategic balanced scorecard — a destination statement across financial/external/internal/learning perspectives, connected to OKRs, KPIs, and CSFs — grounded in joelparkerhenderson/strategic-balanced-scorecard, as distinct from the plain OKR or KPI frameworks it connects.
Total Project Control — Use when asked to explain or apply Total Project Control (TPC) — Stephen Devaux's ROI-focused project-management method, critical path drag, DIPP, and Value Breakdown Structure — sourced from Wikipedia's Total project control article, as distinct from the plain Critical Path Method (see critical-path).
Vision Mission Values — Use when asked to write a vision statement, mission statement, or set of organizational values — the three foundational components of a company's strategic plan — as distinct from a North Star metric (see north-star) or BHAG (see big-hairy-audacious-goal), which operationalize a vision into something trackable.
Voice of the Customer — Use when asked to capture and act on customer feedback — VoC channels (surveys, focus groups, support interactions, social media) feeding product decisions — as the customer-facing input that grounds objective-setting (see objectives-and-key-results) and product management (see product-management) in real user need.
Volatile Uncertain Complex Ambiguous — Use when asked to apply the VUCA framework (Volatile, Uncertain, Complex, Ambiguous) to describe or navigate a turbulent business environment — as a diagnostic lens for choosing an appropriate response, distinct from applying any one specific strategic framework (see swot-analysis, pestle-analysis) without first identifying which VUCA dimension is actually at play.

Change management 6

ADKAR — Use when asked to plan organizational change adoption at the individual level — Awareness, Desire, Knowledge, Ability, Reinforcement (Prosci's ADKAR model) — as the individual-change-adoption complement to process-improvement methodologies like Kaizen and DMAIC (see kaizen, dmaic), which improve the process itself rather than how people adopt it.
Critical to Quality — Use when asked to define Critical to Quality (CTQ) requirements in a Six Sigma context — translating customer expectations into measurable product/service characteristics with performance targets — as distinct from the general SQA catalog (see system-quality-attributes) and feeding directly into a dmaic project's Define/Measure stages.
DMAIC — Use when asked to run a Six Sigma DMAIC improvement project — Define, Measure, Analyze, Improve, Control — as a data-driven, project-scoped alternative to Kaizen's continuous, incremental cycle (see kaizen) or PDCA's general iterative loop (see plan-do-check-act).
Kaizen — Use when asked to apply Kaizen — continuous, incremental, all-employee process improvement built on the Plan-Do-Check-Act cycle (see plan-do-check-act) — as distinct from a project-scoped Six Sigma DMAIC effort (see dmaic), which is heavier-weight and typically team-led rather than everyone-participating.
Six Sigma — Use when asked about the Six Sigma quality-management methodology as a whole — belt-level roles, sigma levels/defects-per-million, and choosing between DMAIC (improving an existing process, see dmaic) or DMADV/DFSS (designing a new one) — as distinct from running the DMAIC cycle itself, which this skill defers to for the step-by-step improvement procedure.
Vanguard Method — Use when asked to apply the Vanguard Method (John Seddon's systems-thinking approach) to redesign a service organization — studying demand, flow, and capability as an integrated system before changing anything — as distinct from transplanting a manufacturing-derived methodology like six-sigma onto service work, which the method's originator specifically argues against.

Change management › Agile 18

Agile Charter — Use when asked to run an agile chartering session — collaboratively defining a project's vision, objectives, and working agreement with a diverse stakeholder group — as distinct from a formal project charter document (see project-charter), which is written and approved rather than co-created in a session.
Agile Coaching — Use when asked about the agile coach role — facilitating ceremonies, removing impediments, fostering psychological safety, and evolving from hands-on guidance to strategic coaching as a team matures — as distinct from a Scrum Master's more process-focused role or a traditional project manager (see project-management).
Agile Delivery — Use when asked to run the delivery track of dual-track agile — building, testing, and shipping validated work via a continuous delivery pipeline — as the track that runs alongside, not after, discovery (see agile-discovery), and grounded in continuous delivery's build/test/deploy/release pipeline.
Agile Discovery — Use when asked to run the discovery track of dual-track agile — validating what to build before building it, via problem identification, user personas, and prototyping — as the track that runs alongside, not before, delivery (see agile-delivery), and feeds product-management's broader discipline.
Agile Liftoff — Use when asked to run an agile project liftoff — aligning a team on vision, objectives, stakeholders, and initial plan at project start — as distinct from an agile chartering session's working-agreement focus (see agile-charter) or a formal project charter document (see project-charter).
Agile Principles — Use when asked what the Agile principles are, to check a team practice or process decision against them, or to explain the reasoning behind agile software delivery (as opposed to a specific framework like Scrum or Kanban, which implement these principles rather than being identical to them).
Agile Reflection — Use when asked to run a team reflection or retrospective in the spirit of the 12th Agile Manifesto principle — regular, honest process examination followed by actual behavior change — as distinct from a futurespective's forward-looking scenario exploration (see futurespective), which looks ahead rather than back.
Agile Showcase — Use when asked to run an agile showcase (sprint review) — demonstrating working software to stakeholders on a regular cadence — including whether a team should run one at all, mirroring the same with/without tradeoff agile-standup covers for daily standups.
Agile Standown — Use when asked about an agile "stand-down" — an informal end-of-day or end-of-session closing check-in some teams run as the counterpart to a morning standup (see agile-standup). This is a less standardized, less common practice than the standup itself — verify what a specific team actually means by the term before assuming a fixed format.
Agile Standup — Use when asked to run a daily standup (daily scrum) — the three-question format, timeboxing, and common failure modes — including whether a team should even run one at all, as distinct from a broader agile-coaching engagement (see agile-coaching) that would help diagnose that question.
Disciplined Agile — Use when asked to choose or tailor a team's "way of working" (WoW) with Disciplined Agile (DA) — a goal-driven toolkit of decision points and options spanning multiple lifecycles, rather than one prescribed process — as distinct from adopting a single fixed framework like scrum, scaled-agile-framework, or large-scale-scrum outright.
Extreme Programming — Use when asked to apply Extreme Programming (XP) — pair programming, test-driven development, continuous integration, refactoring, and sustainable pace as the specific engineering practices behind agile delivery — as distinct from scrum's process/role framework, which XP's practices are commonly run inside rather than as a competing alternative.
Kanban — Use when asked to set up or run a Kanban board — columns, work-in-progress limits, continuous flow — as an alternative to Scrum's fixed sprints (see scrum), suited to continuous-flow work rather than timeboxed iterations.
Large Scale Scrum — Use when asked to scale scrum across many teams with LeSS (Large-Scale Scrum) — one Product Backlog, one Product Owner, and one Sprint shared across all teams, deliberately minimizing added roles and process — as distinct from scaled-agile-framework's more prescriptive, role-heavy approach to the same scaling problem.
Scaled Agile Framework — Use when asked to scale agile delivery across many teams with SAFe (Scaled Agile Framework) — Agile Release Trains, PI Planning, and Portfolio/Large Solution/Essential configurations — as distinct from large-scale-scrum's deliberately minimal alternative for the same scaling problem, and from disciplined-agile's goal-driven toolkit approach rather than a single prescribed structure.
Scrum — Use when asked to set up or run Scrum — roles (Product Owner, Scrum Master, Development Team), artifacts (Product Backlog, Sprint Backlog, Increment), and events (sprint planning, daily scrum, review, retrospective) — as a fixed-sprint alternative to Kanban's continuous flow (see kanban).
Scrum of Scrums — Use when asked to coordinate multiple scrum teams working on one product via a Scrum of Scrums meeting — a lightweight cross-team sync sending one ambassador per team — as distinct from adopting a full scaling framework like large-scale-scrum or scaled-agile-framework, which restructure roles and planning rather than just adding a coordination meeting.
Scrumban — Use when asked to run Scrumban — a hybrid blending scrum's planning structure with kanban's continuous-flow board and WIP limits, pulling work on demand rather than committing to a fixed sprint backlog — for a team that needs more structure than pure Kanban but finds Scrum's fixed sprint commitment a poor fit for their work's variability.

Citations 8

Citation Style Ama — Use when asked to cite sources, format in-text citations, or build a reference list in AMA (American Medical Association) citation style, 11th edition, used in medical journals and the clinical sciences; numbered like [[citation-style-vancouver]], but with superscript numbers and its own manual.
Citation Style Apa — Use when asked to cite sources, format in-text citations, or build a reference list in APA (American Psychological Association) citation style, 7th edition, used in psychology, education, the social sciences, nursing, and business; author-date like [[citation-style-harvard]], but with a fixed official manual; unlike the numbered [[citation-style-ieee]] and [[citation-style-vancouver]].
Citation Style Chicago — Use when asked to cite sources, format in-text citations, or build a reference list in Chicago Manual of Style citation, in both of its systems, used in history, the arts, the humanities (notes-bibliography), and the sciences and social sciences (author-date); a style with two systems, unlike the single-system [[citation-style-apa]] and [[citation-style-mla]].
Citation Style Harvard — Use when asked to cite sources, format in-text citations, or build a reference list in Harvard citation style, used in business, the sciences, and the social sciences, especially in the United Kingdom and Australia; author-date like [[citation-style-apa]], but with no single official manual.
Citation Style Ieee — Use when asked to cite sources, format in-text citations, or build a reference list in IEEE (Institute of Electrical and Electronics Engineers) citation style, used in engineering, computer science, and electronics; numbered like [[citation-style-vancouver]], but with initials first and a distinct punctuation pattern.
Citation Style Mla — Use when asked to cite sources, format in-text citations, or build a reference list in MLA (Modern Language Association) citation style, 9th edition, used in literature, languages, the humanities, and cultural studies; author-page rather than author-date like [[citation-style-apa]], with a Works Cited list rather than numbered references.
Citation Style Oscola — Use when asked to cite sources, format in-text citations, or build a reference list in OSCOLA (Oxford Standard for the Citation of Legal Authorities), used in law, especially in the United Kingdom; a footnote-based legal style, unlike the author-date [[citation-style-apa]] and numbered [[citation-style-ieee]].
Citation Style Vancouver — Use when asked to cite sources, format in-text citations, or build a reference list in Vancouver citation style, used in medicine, nursing, and the biomedical sciences; numbered like [[citation-style-ieee]] and [[citation-style-ama]], with a plain, compact reference format.

Clinical workforce 2

Medical Clinical Supervision — Use when asked to explain or structure clinical supervision — regular, protected mentorship and oversight of a nurse or junior doctor by a more senior clinician, supporting both development and patient safety — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult a qualified health care professional.
Medical Nurse Staffing Ratio Planning — Use when asked to explain or structure nurse staffing ratio planning — setting staffing levels against patient acuity and workload rather than a flat headcount, to keep care safe and sustainable — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult a qualified health care professional.

Communication & thinking 7

Always Improving — Use when asked to summarize or apply ideas from popular self-improvement and business books (Grit, Start with Why, The Lean Startup, The Power of Habit, Zero to One, and others) — grounded in joelparkerhenderson/always-improving's curated summary list. Not a substitute for reading the actual books.
Crucial Conversations — Use when asked how to handle a high-stakes, emotionally charged conversation — the CPR/CRIB/AMPP/WWWF frameworks from the "Crucial Conversations" book — grounded in joelparkerhenderson/crucial-conversations, distinct from general team communication norms (see ways-of-working).
Deliberate Practice — Use when asked to design, audit, or fix practice so it actually builds skill — a goal just past current ability, full concentration, immediate specific feedback, and repetition with correction — or when someone has practiced for a long time without improving. Distinct from [[getting-feedback]] (how to receive feedback well), [[always-improving]] (the general habit of continuous improvement), and [[smart-criteria]] (how to word a goal), each of which it draws on.
Getting Feedback — Use when asked how to seek out or receive feedback well — actively soliciting it, listening without immediately defending, separating the signal from delivery, and deciding what to act on — as the complement to giving-feedback.
Giving Feedback — Use when asked to give feedback effectively — being specific and behavior-focused, timing, balancing positive and constructive feedback, and delivering it in a way the recipient can actually act on — as the complement to getting-feedback.
Inclusive Language — Use when asked to write or review text for inclusive language — gender-neutral role names and pronouns, disability-respectful phrasing, or non-gendered technology/business terminology (master/slave, whitelist/blacklist alternatives) — grounded in joelparkerhenderson/inclusive-language. Adapt to the specific audience and context rather than applying mechanically.
Systems Thinking — Use when asked to analyze a problem as an interconnected system — feedback loops, stocks and flows, leverage points — rather than a chain of independent parts, before reaching for a specific method that assumes linear cause-and-effect (as distinct from applying vanguard-method's service-specific application, or causal-analysis-based-on-system-theory's accident-investigation application, of the same underlying discipline).

Consent & end-of-life care 3

Medical Advance Directive — Use when asked to draft, review, or explain an advance directive (living will) or health care proxy designation — a document stating future medical treatment wishes or naming a decision-maker for when a person can't communicate them — for general educational and structural guidance only, not medical or legal advice; requirements vary by jurisdiction — always follow institutional policy and consult the treating clinician and, where legal validity matters, a qualified lawyer.
Medical Do Not Resuscitate Order — Use when asked to document, explain, or structure a do-not-resuscitate (DNR) order — a clinician-written medical order instructing that CPR not be attempted if a patient's heart or breathing stops — for general educational and structural guidance only, not medical or legal advice; requirements vary by jurisdiction — always follow institutional policy and consult the treating clinician and, where legal validity matters, a qualified lawyer.
Medical Informed Consent — Use when asked to document, explain, or structure the informed consent process for a treatment or procedure — the conversation and record confirming a patient understands and voluntarily agrees before it happens — for general educational and structural guidance only, not medical or legal advice; requirements vary by jurisdiction — always follow institutional policy and consult the treating clinician and, where legal validity matters, a qualified lawyer.

Creative thinking 10

Brainstorming — Use when asked to run a brainstorming session well — quantity-over-quality, non-judgmental atmosphere, timeboxing, and capture technique — the foundational technique within the broader creative-thinking toolkit (see creative-thinking).
Creative Thinking — Use when asked which creative-thinking technique fits a situation — an umbrella overview of brainstorming, mind mapping, SCAMPER, random association, analogies, thinking hats, mindful observation, and storyboarding — as the technique-selection layer above ideation's general discipline.
Flowchart — Use when asked to draw a flowchart — start/end, process, decision, connector, and input/output symbols representing a process or workflow's sequence — as distinct from a mind map's radial, associative structure (see mind-map), which suits non-sequential idea structures rather than linear/branching process flow.
Futurespective — Use when asked to run a futurespective — a forward-looking group exercise imagining possible future scenarios to inform current decisions — as the forward-facing counterpart to a retrospective, drawing on scenario planning and SWOT analysis (see swot-analysis).
Ideation — Use when asked to generate ideas or run a brainstorming session — divergent thinking, mind mapping, SCAMPER, and other idea-generation techniques — as the generative phase that precedes evaluation/selection, distinct from decision-making tools like decision-tree used afterward.
Mental Model — Use when asked to apply or explain a mental model — the cognitive frameworks people use to simplify, predict, and reason about a domain — as the general concept underlying more specific frameworks throughout this collection (SWOT, PDCA, OODA, and others are each a named mental model).
Mind Map — Use when asked to build a mind map — a central-idea-with-radiating-branches visual structure for brainstorming, note-taking, or organizing information — one specific technique within the broader ideation toolkit (see ideation).
Oblique Strategies — Use when asked for a creative-block-breaking prompt, or to explain Brian Eno and Peter Schmidt's "Oblique Strategies" card deck — lateral-thinking prompts for getting unstuck on a creative or technical problem — grounded in joelparkerhenderson/oblique-strategies.
Scamper — Use when asked to apply SCAMPER — a seven-prompt checklist (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse) for generating variations on an existing idea — one specific structured technique within the broader creative-thinking toolkit (see creative-thinking).
Thinking Hats — Use when asked to apply the Six Thinking Hats technique — deliberately switching between factual, emotional, critical, optimistic, creative, and process-level thinking modes — one specific structured technique within the broader creative-thinking toolkit (see creative-thinking).

Decision making 15

Adversary — Use when asked to role-play the person or organization that opposes the user, their plan, or their success — a competitor, rival, or someone who benefits from their failure — and lay out exactly where and how they would compete, undermine, or thwart it, including moves the user would not see coming. Distinct from a [[premortem]] (imagines the plan has failed and explains why, with no opposing agent), from [[competitor-analysis]] (describes competitors as they are, not how a motivated one would attack), and from the full [[foresight]] sequence, where it is the fourth stage.
Decision Analysis — Use when asked to carry out a structured, end-to-end analysis of a significant decision under uncertainty — frame the decision, define objectives and alternatives, model uncertainties and values, evaluate, run sensitivity analysis, and decide whether more information is worth buying — as distinct from a single technique such as a [[decision-tree]], [[expected-value-analysis]], or [[weighted-decision-matrix]], which it may use, and from [[game-theory]] (where other parties choose strategically).
Decision Journal — Use when asked to record an important decision at the moment it is made — the situation, options, reasoning, expectations with probabilities, and mental state — and to review it later so the quality of the decision can be judged separately from its outcome and judgment can improve over time; distinct from [[architecture-decision-record]] and [[decision-records]] (shared, formal records of choices for an organization), general [[journaling]], and a [[postmortem]] (analysis of a failure after it happened).
Decision Tree — Use when asked to build a decision tree — a branching structure of decisions and their outcomes, for classification, prediction, or evaluating scenarios — as one structured evaluation tool, distinct from the generative, judgment-free phase of ideation (see ideation) that typically precedes it.
Expected Value Analysis — Use when asked to compare uncertain options by estimating the possible outcomes of each, their probabilities, and their payoffs, then computing the probability-weighted average (expected value) while also examining the spread, worst case, and sensitivity to the estimates — as distinct from a [[decision-tree]] (sequential decisions, though it uses expected value at its nodes), a [[weighted-decision-matrix]] (multiple criteria, no probabilities), and [[bayes-theorem-analysis]] (updating probabilities from evidence).
Foresight — Use when asked to stress-test a plan end to end before executing it — a five-stage sequence of [[premortem]] (autopsy of the failed plan), verdict (most likely vs. most dangerous failure and the biggest hidden assumption), rebuild (a plan with every failure closed off plus a pre-launch checklist with walk-away results), [[adversary]] (the opponent's attack on the rebuilt plan), and [[tripwire]] (a measurable signal and check day per failure). Use for launches, hires, investments, career moves, and projects not yet started; not for a single stage alone, for an incident already happened ([[postmortem]]), or for a plan too early to have a timeline and success definition.
Game Theory — Use when asked to analyze a decision whose outcome depends on what other rational parties will choose — identify the players, their options, payoffs, and information, then find dominant strategies, equilibria, and ways to change the game (commitments, repetition, side payments) — as distinct from [[expected-value-analysis]] (one decision-maker against uncertain nature), a [[decision-tree]] (no strategic opponent), and [[second-order-thinking]] (general downstream consequences without formal payoffs).
OODA Loop — Use when asked to explain or apply the OODA loop (Observe, Orient, Decide, Act) — John Boyd's decision-cycle theory — for business strategy or competitive situations, or to compare it against PDCA/DMAIC — grounded in joelparkerhenderson/ooda-loop.
Premortem — Use when asked to stress-test a plan before committing to it by assuming it has already failed and writing the autopsy — a prospective, failure-first analysis of a plan's likeliest causes of death, the assumptions behind them, and the first warning sign of each — as distinct from a [[postmortem]] (analyzing a failure that already happened), a generic risk list ([[risk-register]]), and the full five-stage [[foresight]] sequence, of which the premortem is the first stage.
Prospect Theory — Use when asked to understand or predict how people actually judge risky choices — evaluating outcomes as gains and losses relative to a reference point, feeling losses more than equal gains, overweighting small probabilities, and being swayed by framing — in order to debug one's own decisions, design offers, or explain surprising behavior; distinct from [[expected-value-analysis]] (the rational benchmark it departs from), [[game-theory]] (strategic interaction), and [[decision-analysis]] (the structured process it can inform).
Regret Minimization — Use when asked to decide a personal or career-scale choice where numbers do not settle it, by imagining oneself at a distant future point (for example age 80, or ten years on) and asking which option would be regretted least — covering regret of action versus inaction, regret of omission, and what the decision reveals about values — as distinct from a [[weighted-decision-matrix]] (quantified criteria), [[premortem]] (assuming a plan failed), and general [[journaling]].
Second Order Thinking — Use when asked to look past the immediate result of a decision to its downstream consequences — the reactions, feedback loops, and side effects that follow the first effect, and then what follows those — to catch decisions that look good now and backfire later; distinct from [[systems-thinking]] (the wider discipline of modeling interacting parts), a [[premortem]] (assumes failure and asks why), and [[strategic-flywheel-effects]] (a specific reinforcing loop).
Tripwire — Use when asked to turn failure modes, dangers, or risks into tripwires — for each one, a single measurable signal that shows it is starting to happen, a threshold, and an exact time or cadence to check — rather than vague "keep an eye on it" monitoring. Distinct from [[key-risk-indicators]] (the general practice of risk metrics across an organization), a [[risk-register]] (which records the risk but not necessarily its trigger), and the full [[foresight]] sequence, where it is the fifth stage.
Two Way Door Decisions — Use when asked to decide how much deliberation, evidence, and approval a decision deserves by classifying it as reversible (a two-way door, decide fast and adjust) or hard to reverse (a one-way door, slow down and verify), and to find ways to turn one-way doors into two-way ones — as distinct from a [[weighted-decision-matrix]] (choosing among options), a [[premortem]] (stress-testing a chosen plan), and [[architecture-decision-record]] (documenting a decision made).
Weighted Decision Matrix — Use when asked to choose among several options against multiple criteria that matter by different amounts — score each option on each criterion, weight the criteria, total the results, and test how sensitive the winner is to the weights — as distinct from a [[decision-tree]] (sequential choices under uncertainty), [[expected-value-analysis]] (a single quantity under probabilities), and a plain pros-and-cons list (unweighted, unstructured).

Digital health 2

Digital Health Guide — Use when asked to find, explain, or apply content from the Digital Health Guide, a handbook of best practices for delivering digital services in health and social care, such as choosing topics for a role or problem, answering questions on clinical safety, information governance, digital inclusion, or delivery, running a team workshop, or assessing maturity. Companion to [[digital-health-metrics]], which covers measurement; for economic questions see [[health-economics-guide]], and for delivery practice in general see [[software-engineering-guide]].
Digital Health Metrics — Use when asked to define, calculate, choose, or interpret a digital health metric, such as patient portal adoption, telehealth visit rate, appointment no-show rate, alert override rate, readmission rate, customer acquisition cost, or ROI and value on investment, or an evaluation framework such as RE-AIM, using the Digital Health Metrics book as the grounded source. Companion to [[digital-health-guide]], which covers delivery practice; for health spending and value see [[health-economics-metrics]].

Enterprise 4

Enterprise Architecture — Use when asked to align an organization's business processes, information systems, and technology infrastructure at the whole-enterprise level — business/information/technology/application architecture — as distinct from a single system's software-architecture.
Enterprise Change Management — Use when asked to plan or run change management for a large organizational change (merger, reorganization, major technology rollout) — planning/implementation/evaluation stages, stakeholder engagement, resistance — as ECM, distinct from the specific change-improvement techniques in dmaic, kaizen, and adkar.
Enterprise Portfolio Project Management — Use when asked to manage an organization's whole project portfolio strategically — identification/prioritization, resource allocation, portfolio-level risk management, performance tracking — as EPPM, a large-organization-scale application of portfolio-management's concepts.
Enterprise Resource Planning — Use when asked about ERP systems — integrated software managing finance, accounting, HR, supply chain, and CRM in one centralized platform — for understanding what an ERP system does, its benefits, and implementation considerations.

Finance 6

Break-Even Analysis — Use when asked to find the break-even point — the sales volume or revenue at which total costs equal total revenue — to sanity-check a price, a new product, or an initiative before committing, as distinct from [[unit-economics]], which asks whether a single customer is profitable rather than when the whole initiative stops losing money.
Budget Forecasting — Use when asked to build or maintain a budget forecast — the ongoing, continuously updated projection of future income and expenses against actuals — as distinct from a budget itself, which is a fixed plan or target set for a period rather than a live projection.
Cap Table — Use when asked to build, read, or explain a capitalization table — who owns what percentage of a company across founders, employees, and investors, and how funding rounds dilute that ownership — as distinct from a [[business-model-canvas]], which describes how the business operates rather than who owns it.
Personal Budget — Use when asked to build or review a personal or household budget — a plan for an individual's or family's own income and spending — distinct from [[budget-forecasting]], which projects revenue and costs for an organization rather than a person or household.
ROI Analysis — Use when asked to calculate or compare the return on investment (ROI) of a decision or initiative — net benefit relative to cost — as distinct from a [[budget-forecasting]] projection, which tracks overall income and expense over time rather than evaluating one specific investment decision.
Unit Economics — Use when asked to analyze or explain the profitability of a business at the level of one customer or unit — lifetime value, acquisition cost, contribution margin — as distinct from a full financial model or [[roi-analysis]] of a single project or investment.

Fitness 22

Balance and Stability Fitness — Use when asked for guidance on balance and stability training — proprioception, single-leg work, and why this matters across ages and fitness levels.
Bodyweight Fitness — Use when asked for guidance on bodyweight training (calisthenics) — progressions, common movement patterns, and building strength without equipment.
Cardio Fitness — Use when asked for guidance on cardiovascular (cardio) fitness training — heart-rate zones, steady-state vs. interval training, and building an aerobic base.
Core Fitness — Use when asked for guidance on core training — training beyond visible abs, anti-extension/rotation work, and how core strength supports other fitness goals.
Crossfit Fitness — Use when asked for guidance on CrossFit-style training — constantly varied, high-intensity functional movement, scaling for beginners, and the role of coaching.
Endurance Fitness — Use when asked for guidance on endurance training — building toward sustained, longer-duration performance (running, cycling, swimming, or multi-sport events).
Flexibility and Mobility Fitness — Use when asked for guidance on flexibility and mobility training — static vs. dynamic stretching, when to use each, and building a mobility routine.
Functional Fitness — Use when asked for guidance on functional fitness training — movements that mimic real-world activities, multi-joint patterns, and training for everyday capability rather than isolated muscle size.
Group Fitness — Use when asked for guidance on group fitness classes — choosing a class type, getting the most from group instruction, and how it compares to solo training.
Hiit Fitness — Use when asked for guidance on HIIT (high-intensity interval training) — structuring work/rest intervals, who it's suited for, and recovery demands.
Home Gym Fitness — Use when asked for guidance on building a home gym — prioritizing equipment, space and budget trade-offs, and getting real training value without a commercial gym.
Injury Prevention Fitness — Use when asked for guidance on injury prevention in fitness training — warm-up, gradual progression, and recognizing early warning signs before they become serious injuries.
Personal Training Fitness — Use when asked for guidance on working with a personal trainer — what to look for in a trainer, how to set goals together, and getting the most value from sessions.
Pilates — Use when asked for guidance on Pilates as a fitness discipline — core-centered control, breath coordination, and mat vs. equipment-based practice.
Powerlifting — Use when asked for guidance on powerlifting — the squat, bench press, and deadlift as a competitive or training discipline, including programming and form fundamentals.
Prenatal Fitness — Use when asked for guidance on prenatal fitness — safe exercise during pregnancy, exercises and positions to modify or avoid, and the importance of medical guidance.
Progress Tracking Fitness — Use when asked for guidance on tracking fitness progress — what metrics to track for different goals, and avoiding over-reliance on any single number.
Recovery and Rest Fitness — Use when asked for guidance on fitness recovery and rest — sleep, rest days, and recognizing overtraining — the often-neglected counterpart to training itself.
Senior Fitness — Use when asked for guidance on fitness training for older adults — balancing strength, balance, and cardiovascular training with safety and mobility considerations.
Sports Nutrition Fitness — Use when asked for guidance on sports/fitness nutrition — protein needs, pre/post-workout fueling, and hydration for training and performance.
Strength Training Fitness — Use when asked for guidance on strength training — progressive overload, compound lifts, and program structure for someone building a resistance-training routine.
Warm Up and Cool Down Fitness — Use when asked for guidance on structuring a workout warm-up and cool-down — what each should include and why both matter for performance and recovery.

Government accountability & engagement 3

Government Constituent Casework — Use when asked to set up or run constituent casework — an elected official's office helping an individual constituent resolve a problem with a government agency (a US member of Congress's district office, a UK MP's constituency office, a local councillor's casework) — distinct from [[government-ombudsman-complaint-investigation]], which investigates whether an agency itself acted unfairly rather than helping someone navigate it.
Government Ombudsman Complaint Investigation — Use when asked to conduct or write up an ombudsman investigation into a complaint that a government body acted unfairly or made a maladministration error — distinct from a legal appeal, since an ombudsman typically examines fairness and process rather than the legal merits of a decision, and usually can only recommend a remedy rather than compel one (details vary by jurisdiction and specific ombudsman scheme).
Government Public Hearing — Use when asked to plan, notice, or run a public hearing — a formal public meeting where a government body takes testimony or comment on a specific matter (a zoning decision, a proposed budget, a piece of legislation) before deciding — distinct from [[government-legislative-testimony]], which is testimony to a legislative committee specifically and typically without general public sign-up.

Government › Operations 7

Government Contract Proposal — Use when asked to write or review a bid responding to a government solicitation for goods or services — distinct from a commercial [[sales-proposal]], since government procurement typically carries formal compliance requirements, published evaluation criteria, and sometimes set-aside programs for specific categories of bidder, all of which vary significantly by country and level of government.
Government Emergency Management Plan — Use when asked to write or review a government emergency management plan — a jurisdiction's plan for coordinating multi-agency response to a civil emergency such as a natural disaster, public health emergency, or major infrastructure failure — distinct from a single organization's [[business-continuity-plan]], which is one organization's internal continuity rather than coordination across multiple agencies and the public.
Government Open Data Publication — Use when asked to plan or review a government open data publication — a government body proactively publishing datasets for public and reuse, on an ongoing basis and with no request required — distinct from [[freedom-of-information-request]], which is a reactive response to one individual's specific request rather than proactive, ongoing publication.
Government Performance Report — Use when asked to write or review a government performance report — a government body's disclosure of its own performance against stated goals or metrics, to a legislature and/or the public — distinct from [[sustainability-report]], which is specifically ESG/environmental-social-governance disclosure rather than broader mission-accountability reporting.
Government Public Budget Appropriation — Use when asked to draft, review, or explain a public budget appropriation — the formal government process of allocating public funds to specific purposes for a budget period — distinct from organizational [[budget-forecasting]], since this is a legislative or political appropriations process where a legislature or council formally authorizes spending, not an internal projection exercise.
Government Public Records Management — Use when asked to advise on or design a government public records management process — how a government body manages the lifecycle of its official records, from creation through retention to disposal or archiving, under whatever public-records retention law applies — noting, in the same vein as [[freedom-of-information-request]]'s treatment of FOI law, that retention schedules and requirements vary significantly by country and agency.
Government Security Clearance Application — Use when asked to advise on applying for or maintaining a government security clearance for a position requiring access to classified or sensitive information — noting that clearance levels, required forms, adjudication criteria, and reciprocity between agencies vary significantly by country and are governed by specific national security law, so this is general structural guidance, not a substitute for the specific agency's own instructions.

Health & safety 4

Care Plan — Use when asked to organize a care plan for an aging or ill family member — a checklist covering legal, medical, financial, and long-term care areas — grounded in joelparkerhenderson/care-plan. This is general organizational guidance, not medical, legal, or financial advice for a specific person's situation.
First Aid — Use when asked for general first-aid knowledge — the primary survey (DRABC/DRSABC), treating bleeding, burns, choking, or shock, or recovery position technique. This is general educational information, not medical advice for a specific person's condition — always direct a real emergency to local emergency services and in-person trained care.
Health Care — Use when asked general questions about how health care systems and terminology work — care tiers (primary/secondary/tertiary), health insurance concepts, patient rights, or navigating a health system. This is general educational information about how health care works, not medical advice, diagnosis, or guidance for a specific person's condition — for symptoms or an actual emergency, see urgent-emergency-care.
Urgent Emergency Care — Use when asked how to recognize a medical emergency, decide between emergency care and urgent/primary care, or what to say when calling emergency services. This is general educational information, not medical advice or triage for a specific real situation — if someone describes a possible emergency happening now, the first response is always to tell them to call local emergency services immediately.

Health care 75

Allergy Care — Use when asked for general educational information about allergy care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Alzheimers Disease Care — Use when asked for general educational information about Alzheimer's disease care — common symptoms, general self-care and caregiving measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Anxiety Care — Use when asked for general educational information about anxiety care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Arthritis Care — Use when asked for general educational information about arthritis care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Attention Deficit Care — Use when asked for general educational information about ADHD (attention deficit) care — common symptoms, general self-care and management measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Autism Care — Use when asked for general educational information about autism care and support — common characteristics, general support measures, and when to seek professional guidance — for education only, not medical advice; always direct the reader to consult a doctor or relevant specialist.
Bipolar Care — Use when asked for general educational information about bipolar disorder care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or mental health professional.
Cancer Care — Use when asked for general educational information about cancer care — common symptoms, general self-care during treatment, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Cold Sore Care — Use when asked for general educational information about cold sore (oral herpes) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Concussion Care — Use when asked for general educational information about concussion care — common symptoms, general self-care measures, and when to seek urgent medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Croup Care — Use when asked for general educational information about croup care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Dehydration Care — Use when asked for general educational information about dehydration care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Dementia Care — Use when asked for general educational information about dementia care — common symptoms, general self-care and caregiving measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Dental Care — Use when asked for general educational information about dental/oral health care — common issues, general self-care measures, and when to seek dental attention — for education only, not medical/dental advice; always direct the reader to consult a dentist or health care professional.
Depression Care — Use when asked for general educational information about depression care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Diabetes Care — Use when asked for general educational information about diabetes care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Earache Care — Use when asked for general educational information about earache care — common causes, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Eczema Care — Use when asked for general educational information about eczema (atopic dermatitis) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Endometriosis Care — Use when asked for general educational information about endometriosis care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Eye Care — Use when asked for general educational information about eye care — common issues, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult an eye care professional or doctor.
Fever Care — Use when asked for general educational information about fever care — common causes, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Flu Care — Use when asked for general educational information about flu (influenza) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Frozen Shoulder Care — Use when asked for general educational information about frozen shoulder (adhesive capsulitis) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Gallstone Care — Use when asked for general educational information about gallstone care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Gonorrhea Care — Use when asked for general educational information about gonorrhea care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Gout Care — Use when asked for general educational information about gout care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Hay Fever Care — Use when asked for general educational information about hay fever (allergic rhinitis) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Heart Disease Care — Use when asked for general educational information about heart disease care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Hernia Care — Use when asked for general educational information about hernia care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Herpes Care — Use when asked for general educational information about (genital) herpes care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Hypertension Care — Use when asked for general educational information about hypertension (high blood pressure) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Indigestion Care — Use when asked for general educational information about indigestion (dyspepsia) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Joint Hypermobility Care — Use when asked for general educational information about joint hypermobility care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Kidney Stone Care — Use when asked for general educational information about kidney stone care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Laryngitis Care — Use when asked for general educational information about laryngitis care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Lice Care — Use when asked for general educational information about head lice care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Lupus Care — Use when asked for general educational information about lupus care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Lyme Disease Care — Use when asked for general educational information about Lyme disease care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Malaria Care — Use when asked for general educational information about malaria care — common symptoms, general self-care and prevention measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Malnutrition Care — Use when asked for general educational information about malnutrition care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Mast Cell Activation Syndrome Care — Use when asked for general educational information about Mast Cell Activation Syndrome (MCAS) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Mental Health Care — Use when asked for general educational information about mental health care — general principles, self-care measures, and when to seek professional help — for education only, not medical advice; always direct the reader to consult a doctor or mental health professional.
Migraine Care — Use when asked for general educational information about migraine care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Mumps Care — Use when asked for general educational information about mumps care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Norovirus Care — Use when asked for general educational information about norovirus care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Obesity Care — Use when asked for general educational information about obesity care — general principles, self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Panic Care — Use when asked for general educational information about panic attack/panic disorder care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Parkinsons Disease Care — Use when asked for general educational information about Parkinson's disease care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Phobia Care — Use when asked for general educational information about phobia care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or mental health professional.
Pneumonia Care — Use when asked for general educational information about pneumonia care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Psoriasis Care — Use when asked for general educational information about psoriasis care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Ringworm Care — Use when asked for general educational information about ringworm care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Rosacea Care — Use when asked for general educational information about rosacea care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Scabies Care — Use when asked for general educational information about scabies care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Sciatica Care — Use when asked for general educational information about sciatica care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Sepsis Care — Use when asked for general educational information about sepsis — recognizing symptoms and the need for emergency care — for education only, not medical advice; always direct the reader to consult a doctor or health care professional, and to treat suspected sepsis as a medical emergency.
Shingles Care — Use when asked for general educational information about shingles care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Sinusitis Care — Use when asked for general educational information about sinusitis care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Sleep Apnea Care — Use when asked for general educational information about sleep apnea care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Sore Throat Care — Use when asked for general educational information about sore throat care — common causes, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Stomache Ache Care — Use when asked for general educational information about stomach ache care — common causes, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Streptococcus Care — Use when asked for general educational information about streptococcal (strep) infection care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Sunburn Care — Use when asked for general educational information about sunburn care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Syphilis Care — Use when asked for general educational information about syphilis care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Tennis Elbow Care — Use when asked for general educational information about tennis elbow (lateral epicondylitis) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Thrush Care — Use when asked for general educational information about thrush (candidiasis) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Tick Bite Care — Use when asked for general educational information about tick bite care — proper tick removal, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Tinnitus Care — Use when asked for general educational information about tinnitus care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Tonsillitis Care — Use when asked for general educational information about tonsillitis care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Toothache Care — Use when asked for general educational information about toothache care — common causes, general self-care measures, and when to seek dental attention — for education only, not medical/dental advice; always direct the reader to consult a dentist or health care professional.
Urinary Tract Infection Care — Use when asked for general educational information about urinary tract infection (UTI) care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Vertigo Care — Use when asked for general educational information about vertigo care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Wart Care — Use when asked for general educational information about wart care — common symptoms, general self-care measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Yellow Fever Care — Use when asked for general educational information about yellow fever care — common symptoms, general self-care and prevention measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.
Zika Care — Use when asked for general educational information about Zika virus care — common symptoms, general self-care and prevention measures, and when to seek medical attention — for education only, not medical advice; always direct the reader to consult a doctor or health care professional.

Health care assessments 83

Allergy Assessment — Use when asked to administer, score, or explain an Allergy Assessment — a comprehensive drug/food/environmental allergy evaluation with anaphylaxis risk grading — grounded in FormExamples/form-examples.
Anesthesiology Assessment — Use when asked to administer, score, or explain an Anesthesiology Assessment — combining ASA Physical Status, Mallampati/airway score, Revised Cardiac Risk Index, and STOP-BANG into a composite perioperative risk level — grounded in FormExamples/form-examples; closely related to pre-anaesthesia-assessment and pre-operative-assessment-by-clinician.
Asthma Assessment — Use when asked to administer, score, or explain an Asthma Assessment — using the ACT (Asthma Control Test) — grounded in FormExamples/form-examples.
Attention Deficit Assessment — Use when asked to administer, score, or explain an Attention Deficit Assessment — ADHD screening using the ASRS v1.1 screener — grounded in FormExamples/form-examples.
Audio Vestibular Assessment — Use when asked to administer, score, or explain an Audio-Vestibular Assessment — combined audiology and balance evaluation using WHO hearing-loss grading and the Dizziness Handicap Inventory (DHI) — grounded in FormExamples/form-examples; related to audiology-assessment and hearing-aid-assessment.
Audiology Assessment — Use when asked to administer, score, or explain an Audiology Assessment — comprehensive hearing evaluation graded by pure tone average — grounded in FormExamples/form-examples; related to audio-vestibular-assessment and hearing-aid-assessment.
Autism Assessment — Use when asked to administer, score, or explain an Autism Assessment — screening with the AQ-10 questionnaire plus sensory/developmental profiling — grounded in FormExamples/form-examples.
Birth Control Assessment — Use when asked to administer, score, or explain a Birth Control Assessment — contraceptive suitability using UK Medical Eligibility Criteria (UK MEC) — grounded in FormExamples/form-examples; closely related to contraception-assessment.
Blood Donation Assessment — Use when asked to administer, score, or explain a Blood Donation Assessment — eligibility screening aligned with UK NHSBT's JPAC Donor Selection Guidelines — grounded in FormExamples/form-examples.
Bone Marrow Donation Assessment — Use when asked to administer, score, or explain a Bone Marrow Donation Assessment — haematopoietic stem cell donor evaluation with HLA typing and collection-method suitability — grounded in FormExamples/form-examples.
Caprini Venous Thromboembolism Risk Assessment — Use when asked to administer, score, or explain the Caprini Venous Thromboembolism Risk Assessment — a weighted risk-factor checklist for surgical/medical inpatients, scored 0+ and banded into a prophylaxis recommendation — grounded in FormExamples/form-examples; related to padua-venous-thromboembolism-risk-assessment.
Cardiology Assessment — Use when asked to administer, score, or explain a Cardiology Assessment — using CCS Angina Classification and NYHA Heart Failure Classification — grounded in FormExamples/form-examples.
Cognitive Assessment — Use when asked to administer, score, or explain a Cognitive Assessment — screening with the MMSE (Mini-Mental State Examination) — grounded in FormExamples/form-examples; distinct from confusion-assessment-method's acute-delirium focus.
Confusion Assessment Method — Use when asked to administer, score, or explain the Confusion Assessment Method (CAM) — a bedside delirium screening algorithm (present/absent, not a numeric score) with a CAM-ICU variant for ventilated patients — grounded in FormExamples/form-examples; distinct from cognitive-assessment's chronic-impairment focus.
Contraception Assessment — Use when asked to administer, score, or explain a Contraception Assessment — eligibility screening across 11 methods using UK Medical Eligibility Criteria (UKMEC) — grounded in FormExamples/form-examples; closely related to birth-control-assessment.
Dental Assessment — Use when asked to administer, score, or explain a Dental Assessment — oral health evaluation using the DMFT Index — grounded in FormExamples/form-examples.
Dermatology Assessment — Use when asked to administer, score, or explain a Dermatology Assessment — quality-of-life evaluation using the DLQI plus lesion characterization — grounded in FormExamples/form-examples.
Diabetes Assessment — Use when asked to administer, score, or explain a Diabetes Assessment — a structured NICE-aligned diabetes review covering glycaemic control, complications, and cardiovascular risk — grounded in FormExamples/form-examples; related to diabetes-podiatry-assessment.
Diabetes Podiatry Assessment — Use when asked to administer, score, or explain a Diabetes Podiatry Assessment — diabetic foot screening for neuropathy, ischaemia, and ulcer risk — related to diabetes-assessment's broader annual review; general clinical knowledge (the FormExamples/form-examples source for this specific form is not yet populated).
Dietic Assessment — Use when asked to administer, score, or explain a Dietetic Assessment — a dietitian-driven nutritional evaluation computing a MUST score and GLIM malnutrition diagnosis — grounded in FormExamples/form-examples; related to nutrition-assessment.
Dyslexia Assessment — Use when asked to administer, score, or explain a Dyslexia Assessment — a specific learning difficulty evaluation using standardized reading/writing/phonological scores — grounded in FormExamples/form-examples.
Endocrinology Assessment — Use when asked to administer, score, or explain an Endocrinology Assessment — a general endocrine consultation covering thyroid, adrenal, glucose, reproductive, pituitary, and bone/calcium axes — grounded in FormExamples/form-examples.
Endometriosis Assessment — Use when asked to administer, score, or explain an Endometriosis Assessment — revised ASRM staging plus EHP-30 quality-of-life scoring — grounded in FormExamples/form-examples.
Ergonomic Assessment — Use when asked to administer, score, or explain an Ergonomic Assessment — workplace musculoskeletal risk using REBA (Rapid Entire Body Assessment) — grounded in FormExamples/form-examples.
Fall Risk Assessment — Use when asked to administer, score, or explain a Fall Risk Assessment — using the Morse Fall Scale (MFS) — grounded in FormExamples/form-examples; related to mobility-assessment.
Fertility Assessment — Use when asked to administer, score, or explain a Fertility Assessment — a NICE CG156-aligned sub-fertility evaluation covering reproductive history, hormonal profile, and partner factors — grounded in FormExamples/form-examples.
First Responder Assessment — Use when asked to administer, score, or explain a First Responder Assessment — fitness/competency evaluation for paramedics, EMTs, and first aiders — grounded in FormExamples/form-examples.
Gastroenterology Assessment — Use when asked to administer, score, or explain a Gastroenterology Assessment — GI symptom evaluation with red-flag detection — grounded in FormExamples/form-examples.
Genetic Assessment — Use when asked to administer, score, or explain a Genetic Assessment — genetic counselling referral using weighted risk factor scoring across cancer, cardiovascular, neuro, and reproductive genetics — grounded in FormExamples/form-examples; closely related to genetics-assessment.
Genetics Assessment — Use when asked to administer, score, or explain a Genetics Assessment — clinical genetics evaluation with a three-generation pedigree and targeted risk scoring (Manchester Score, Bethesda criteria) — grounded in FormExamples/form-examples; closely related to genetic-assessment.
Gerontology Assessment — Use when asked to administer, score, or explain a Gerontology Assessment — an elderly-patient evaluation using the Clinical Frailty Scale (CFS) — grounded in FormExamples/form-examples.
Gynecology Assessment — Use when asked to administer, score, or explain a Gynecology Assessment — a general gynaecological symptom evaluation covering menstrual, cervical-screening, obstetric, and sexual health history — grounded in FormExamples/form-examples.
Hearing Aid Assessment — Use when asked to administer, score, or explain a Hearing Aid Assessment — hearing-aid candidacy using the HHIE-S questionnaire — grounded in FormExamples/form-examples; related to audiology-assessment and audio-vestibular-assessment.
Hematology Assessment — Use when asked to administer, score, or explain a Hematology Assessment — full blood count, coagulation, and haemoglobinopathy evaluation with a composite haematological risk classification — grounded in FormExamples/form-examples.
Hormone Replacement Therapy Assessment — Use when asked to administer, score, or explain a Hormone Replacement Therapy Assessment — HRT eligibility and symptom evaluation using the Menopause Rating Scale (MRS) — grounded in FormExamples/form-examples.
Integumentary Assessment — Use when asked to administer, score, or explain an Integumentary Assessment — skin/hair/nails evaluation combining a head-to-toe inspection with the Braden Scale for pressure ulcer risk — grounded in FormExamples/form-examples; related to waterlow-pressure-ulcer-risk-assessment and dermatology-assessment.
Kinesiology Assessment — Use when asked to administer, score, or explain a Kinesiology Assessment — functional movement screening using the FMS (Functional Movement Screen) — grounded in FormExamples/form-examples.
Learning Disability Assessment — Use when asked to administer, score, or explain a Learning Disability Assessment — an NHS England Annual Health Check aligned with DSM-5-TR/ICD-11 criteria, producing a severity category and Health Action Plan — grounded in FormExamples/form-examples.
Mast Cell Activation Syndrome Assessment — Use when asked to administer, score, or explain a Mast Cell Activation Syndrome (MCAS) Assessment — multi-system symptom evaluation with trigger identification — grounded in FormExamples/form-examples.
Medical Language Speaking Assessment for Cymraeg — Use when asked to administer, score, or explain a Medical Language Speaking Assessment for Cymraeg — clinical Welsh-language speaking assessment mapped to CEFR levels — grounded in FormExamples/form-examples; the Welsh-language counterpart to medical-language-speaking-assessment-for-english.
Medical Language Speaking Assessment for English — Use when asked to administer, score, or explain a Medical Language Speaking Assessment for English — modelled on the OET Medicine speaking sub-test — grounded in FormExamples/form-examples; the English-language counterpart to medical-language-speaking-assessment-for-cymraeg.
Mental Health Act Assessment — Use when asked to administer or explain a Mental Health Act Assessment — the UK Mental Health Act 1983/2007 statutory detention assessment by an AMHP and two doctors — grounded in FormExamples/form-examples; a legal completeness check, not a numeric score, distinct from mental-health-assessment.
Mental Health Assessment — Use when asked to administer, score, or explain a Mental Health Assessment — combined depression/anxiety screening using PHQ-9 and GAD-7 — grounded in FormExamples/form-examples; distinct from the legal/procedural mental-health-act-assessment.
Mobility Assessment — Use when asked to administer, score, or explain a Mobility Assessment — balance and gait evaluation using the Tinetti Assessment Tool — grounded in FormExamples/form-examples; related to fall-risk-assessment.
Neurology Assessment — Use when asked to administer, score, or explain a Neurology Assessment — general neurological evaluation using the NIHSS plus headache/seizure/motor/sensory/cognitive assessment — grounded in FormExamples/form-examples; closely related to stroke-assessment.
Nutrition Assessment — Use when asked to administer, score, or explain a Nutrition Assessment — nutritional status evaluation using the Malnutrition Universal Screening Tool (MUST) — grounded in FormExamples/form-examples; closely related to dietic-assessment.
Obstetrics Assessment — Use when asked to administer, score, or explain an Obstetrics Assessment — a NICE NG201-aligned antenatal risk stratification driving the care pathway — grounded in FormExamples/form-examples; related to prenatal-assessment.
Occupational Therapy Assessment — Use when asked to administer, score, or explain an Occupational Therapy Assessment — functional performance across self-care, productivity, and leisure using the COPM — grounded in FormExamples/form-examples.
Oncology Assessment — Use when asked to administer, score, or explain an Oncology Assessment — cancer patient evaluation using ECOG Performance Status — grounded in FormExamples/form-examples.
Ophthalmology Assessment — Use when asked to administer, score, or explain an Ophthalmology Assessment — visual acuity, anterior/posterior segment, and visual field evaluation — grounded in FormExamples/form-examples.
Organ Donation Assessment — Use when asked to administer, score, or explain an Organ Donation Assessment — medical suitability, organ function, and immunological compatibility for living and deceased donors — grounded in FormExamples/form-examples.
Orthopedic Assessment — Use when asked to administer, score, or explain an Orthopaedic Assessment — musculoskeletal evaluation using the DASH questionnaire — grounded in FormExamples/form-examples.
Otolaryngology Assessment — Use when asked to administer, score, or explain an Otolaryngology Assessment — general ENT consultation using the SNOT-22 symptom score — grounded in FormExamples/form-examples.
Padua Venous Thromboembolism Risk Assessment — Use when asked to administer, score, or explain the Padua Venous Thromboembolism Risk Assessment (Padua Prediction Score) — an 11-factor weighted VTE risk tool for hospitalized medical patients, scored 0-20 with a ≥4 high-risk threshold — grounded in FormExamples/form-examples; related to caprini-venous-thromboembolism-risk-assessment.
Palliative Assessment — Use when asked to administer, score, or explain a Palliative Assessment — symptom-focused evaluation using the Edmonton Symptom Assessment System-revised (ESAS-r) — grounded in FormExamples/form-examples.
Pediatric Assessment — Use when asked to administer, score, or explain a Pediatric Assessment — child development screening covering growth, milestones, and immunization — grounded in FormExamples/form-examples.
Plastic Surgery Assessment — Use when asked to administer, score, or explain a Plastic Surgery Assessment — reconstructive/aesthetic surgery candidacy using ASA Physical Status, wound classification, and surgical complexity scoring — grounded in FormExamples/form-examples.
Post Traumatic Stress Assessment — Use when asked to administer, score, or explain a Post-Traumatic Stress Assessment — DSM-5-aligned PTSD screening using the PCL-5 — grounded in FormExamples/form-examples.
Pre Anaesthesia Assessment — Use when asked to administer, score, or explain a Pre-Anaesthesia Assessment — a UK NHS-aligned clinician-driven pre-op assessment computing ASA grade and composite perioperative risk — grounded in FormExamples/form-examples; near-identical in scope to pre-operative-assessment-by-clinician.
Pre Operative Assessment By Clinician — Use when asked to administer, score, or explain a Pre-operative Assessment by Clinician — a UK NHS-aligned clinician-driven pre-op assessment computing ASA grade and composite perioperative risk — grounded in FormExamples/form-examples; the clinician counterpart to pre-operative-assessment-by-patient, near-identical to pre-anaesthesia-assessment.
Pre Operative Assessment By Patient — Use when asked to administer, score, or explain a Pre-operative Assessment by Patient — a UK NHS-aligned patient self-report questionnaire computing an ASA grade — grounded in FormExamples/form-examples; the patient counterpart to pre-operative-assessment-by-clinician.
Prenatal Assessment — Use when asked to administer, score, or explain a Prenatal Assessment — general antenatal evaluation with Low/Moderate/High risk stratification — grounded in FormExamples/form-examples; related to obstetrics-assessment.
Psychiatry Assessment — Use when asked to administer, score, or explain a Psychiatry Assessment — comprehensive evaluation using the GAF (Global Assessment of Functioning) Scale with mental status exam, risk, and capacity — grounded in FormExamples/form-examples.
Psychology Assessment — Use when asked to administer, score, or explain a Psychology Assessment — general screening using the DASS-21 (Depression Anxiety Stress Scales) — grounded in FormExamples/form-examples.
Pulmonology Assessment — Use when asked to administer, score, or explain a Pulmonology Assessment — respiratory evaluation using GOLD staging for COPD — grounded in FormExamples/form-examples; related to respirology-assessment.
Quick Sequential Organ Failure Assessment — Use when asked to administer, score, or explain the Quick Sequential Organ Failure Assessment (qSOFA) — a 3-criterion bedside sepsis-risk screen scored 0-3 with a ≥2 escalation threshold — grounded in FormExamples/form-examples; the bedside-screening counterpart to sequential-organ-failure-assessment.
Renal Assessment — Use when asked to administer, score, or explain a Renal Assessment — CKD staging using the KDIGO GFR x albuminuria heatmap — grounded in FormExamples/form-examples.
Respirology Assessment — Use when asked to administer, score, or explain a Respirology Assessment — respiratory evaluation using the MRC Dyspnoea Scale — grounded in FormExamples/form-examples; related to pulmonology-assessment.
Rheumatology Assessment — Use when asked to administer, score, or explain a Rheumatology Assessment — disease activity evaluation using DAS28 — grounded in FormExamples/form-examples.
Seasonal Affective Disorder Assessment — Use when asked to administer, score, or explain a Seasonal Affective Disorder Assessment — combined SPAQ Global Seasonality Score and PHQ-9 evaluation — grounded in FormExamples/form-examples.
Semaglutide Assessment — Use when asked to administer, score, or explain a Semaglutide Assessment — GLP-1 receptor agonist eligibility screening — grounded in FormExamples/form-examples.
Sequential Organ Failure Assessment — Use when asked to administer, score, or explain the Sequential Organ Failure Assessment (SOFA) — six organ-system sub-scores (0-4 each) summing to a 0-24 total, tracked as delta-SOFA and used in Sepsis-3 criteria — grounded in FormExamples/form-examples; the definitive counterpart to quick-sequential-organ-failure-assessment.
Sleep Quality Assessment — Use when asked to administer, score, or explain a Sleep Quality Assessment — using the Pittsburgh Sleep Quality Index (PSQI) — grounded in FormExamples/form-examples.
Sports Medicine Assessment — Use when asked to administer, score, or explain a Sports Medicine Assessment — a pre-participation physical evaluation (PPE) for athletes — grounded in FormExamples/form-examples.
Stroke Assessment — Use when asked to administer, score, or explain a Stroke Assessment — acute stroke evaluation using the NIHSS with symptom-onset timing — grounded in FormExamples/form-examples; closely related to neurology-assessment.
Substance Abuse Assessment — Use when asked to administer, score, or explain a Substance Abuse Assessment — combined AUDIT (alcohol) and DAST-10 (drug) evaluation — grounded in FormExamples/form-examples.
Sundowner Syndrome Assessment — Use when asked to administer, score, or explain a Sundowner Syndrome Assessment — evaluation using the Cohen-Mansfield Agitation Inventory and Neuropsychiatric Inventory — grounded in FormExamples/form-examples.
Urology Assessment — Use when asked to administer, score, or explain a Urology Assessment — evaluation using the International Prostate Symptom Score (IPSS) — grounded in FormExamples/form-examples.
Vaccinations Assessment — Use when asked to administer, score, or explain a Vaccinations Assessment — immunization-schedule compliance aligned with the UK Green Book — grounded in FormExamples/form-examples.
Waterlow Pressure Ulcer Risk Assessment — Use when asked to administer, score, or explain the Waterlow Pressure Ulcer Risk Assessment — a summed weighted-category score where higher total means higher risk — grounded in FormExamples/form-examples; the inverse-scaled counterpart to integumentary-assessment's Braden Scale.
Workplace Climate Assessment — Use when asked to administer, score, or explain a Workplace Climate Assessment — organizational culture and psychological safety measured with a normalized Likert-scale index — grounded in FormExamples/form-examples; related to workplace-stress-assessment and workplace-safety-assessment.
Workplace Safety Assessment — Use when asked to administer, score, or explain a Workplace Safety Assessment — a UK HSE-aligned safety audit checklist for healthcare settings — grounded in FormExamples/form-examples; related to ergonomic-assessment and workplace-climate-assessment.
Workplace Stress Assessment — Use when asked to administer, score, or explain a Workplace Stress Assessment — using the UK HSE Management Standards Indicator Tool across seven domains — grounded in FormExamples/form-examples; related to workplace-climate-assessment.

Health economics 2

Health Economics Guide — Use this skill when a reader wants to apply the Health Economics Guide book to a real question — find the right chapter, get a grounded answer, run a team workshop, assess organizational maturity, or pull an action checklist. For general users of the guide (executives, directors, product/programme leads, clinical and operational managers) — not for editing the book itself; see health-economics-guide-maintainer for that. Trigger on "which chapter covers...", "what does the guide say about...", "help me think through X using health economics", "run a workshop on...", "where is Y addressed".
Health Economics Metrics — Answer health economics questions and build cost/value arguments (QALYs, ICER, ROI, Cost of Delay, business cases for NHS/health software) using this repo's topics/ as the grounded source of formulas, worked examples, and pitfalls. Use when the user asks to explain a health-economics concept, compute a metric, justify a health-software investment, or write a business case for a national health service audience.

Hiring 11

Cover Letter — Use when asked to write a cover letter — the narrative document submitted alongside a resume, covering an opening hook, why this role and company, relevant highlights, and a closing — as distinct from the resume itself, which lists structured facts rather than telling a story.
Employee Onboarding — Use when asked to plan employee onboarding — pre-start logistics through the first 90 days for a new hire — picking up after a signed offer letter, as distinct from the offer letter itself, which commits to terms rather than planning what happens once the person actually starts.
Exit Interview — Use when asked to design or conduct an exit interview — the conversation or survey held when someone leaves, aimed at honest feedback about why and what could improve — as distinct from the offboarding-checklist, which handles departure logistics like access and equipment rather than gathering feedback.
Interview Scorecard — Use when asked to build or fill out an interview scorecard — defined criteria, a consistent rating scale, and evidence fields an interviewer completes right after talking to a candidate — as the comparable, defensible alternative to an unstructured post-interview writeup or a gut-feel recommendation.
Job Description — Use when asked to write or revise a job description — title, summary, responsibilities, qualifications, reporting line, and compensation — as the durable internal definition of a role, distinct from a job posting (see below), which is the external, persuasive advertisement drawn from it.
Job Description With Uk Gdad Pcf and Agenda for Change — Use when drafting a job description for an NHS (or wider UK public sector) digital, data, or technology role that needs to combine the UK Government Digital and Data (GDAD) Profession Capability Framework for role content and skill levels with the NHS Agenda for Change job evaluation scheme for banding — e.g. "write a JD for a Band 7 senior data analyst," "turn this DDaT role profile into an NHS job description," or "what band should this GDAD level map to."
Job Posting — Use when asked to write or adapt a job posting — the external, persuasive advertisement aimed at candidates, drawn from an existing job description — as distinct from the job description itself (see below), which is the internal, durable definition of the role the posting gets adapted from.
Offboarding Checklist — Use when asked to build or run an employee departure checklist — access revocation, equipment return, knowledge transfer, final pay, and team communication — for a voluntary or involuntary exit, as distinct from the exit-interview conversation itself, which captures feedback rather than executing logistics.
Offer Letter — Use when asked to write a formal offer letter — title, compensation, start date, reporting line, and contingencies — extended to a candidate after a hiring decision, as distinct from the job posting that recruited them and the job description that defines the role, both of which precede it rather than commit to specific terms with a named person.
Performance Improvement Plan — Use when asked to write or structure a performance improvement plan (PIP) — a formal, time-boxed remediation plan for specific underperformance — as distinct from a routine performance-review-meeting, which evaluates performance broadly rather than fixing a defined problem on a deadline.
Resume — Use when asked to write, revise, or tailor a resume (US) or CV (UK/international) — contact info, summary, experience, education, and skills — as the candidate-side document submitted to apply for a role, distinct from a cover letter, which is narrative rather than structured, and tailored against a job description or job posting rather than being one.

Hobbies 33

3D Printing — Use when asked for guidance on 3D printing as a hobby — printer types, materials, and common print-quality troubleshooting for someone starting out.
Amateur Radio — Use when asked for guidance on amateur (ham) radio as a hobby — getting licensed, choosing basic equipment, and what to do once on the air.
Astronomy — Use when asked for guidance on amateur astronomy/stargazing as a hobby — choosing equipment (or none at all), finding dark skies, and what to observe first.
Baking — Use when asked for guidance on baking as a hobby — the role of precise measurement, key techniques like proofing and creaming, and common beginner mistakes.
Beekeeping — Use when asked for guidance on beekeeping as a hobby — basic hive setup, seasonal management, and local regulations for someone starting out.
Birdwatching — Use when asked for guidance on birdwatching (birding) as a hobby — basic equipment, identification technique, and how to get started locally.
Board Gaming — Use when asked for guidance on tabletop/board gaming as a hobby — how to choose games for a group, teach rules effectively, and build a game collection.
Calligraphy — Use when asked for guidance on calligraphy as a hobby — materials (pens, ink), basic letterform practice, and how to develop consistent style.
Camping — Use when asked for guidance on camping as a hobby — essential gear, campsite selection, and safety basics for someone starting out, from car camping to backpacking.
Chess — Use when asked for guidance on chess as a hobby — the fastest ways to improve, common beginner mistakes, and how to structure practice.
Coin Collecting — Use when asked for guidance on coin collecting (numismatics) as a hobby — how to start a collection, grading and authentication basics, and proper storage.
Cycling — Use when asked for guidance on cycling as a recreational or fitness hobby — bike fit, basic maintenance, and safety fundamentals for someone starting out.
Drawing — Use when asked for guidance on drawing as a hobby — materials, fundamentals like proportion and shading, and how to practice effectively as a beginner.
Fishing — Use when asked for guidance on fishing as a hobby — basic gear, technique, and local regulations for someone starting out.
Gardening — Use when asked for guidance on gardening as a hobby — soil, sunlight, watering, and getting started with a first garden bed or container.
Genealogy — Use when asked for guidance on genealogy (family history research) as a hobby — starting the research, evaluating sources, and organizing findings.
Geocaching — Use when asked for guidance on geocaching as a hobby — using GPS coordinates to find hidden containers, basic etiquette, and getting started.
Hiking — Use when asked for guidance on hiking as a hobby — trail selection, essential gear, and safety basics for someone starting out.
Home Brewing — Use when asked for guidance on home brewing as a hobby — the basic beer-brewing process, equipment, and the importance of sanitation for someone starting out.
Journaling — Use when asked for guidance on journaling as a hobby — different journaling styles, how to build a consistent habit, and getting past a blank page.
Knitting — Use when asked for guidance on knitting as a hobby — basic stitches, materials, and how to start a first project.
Leatherworking — Use when asked for guidance on leatherworking as a hobby — leather types, basic tools, and stitching/edge-finishing technique for someone starting out.
Model Building — Use when asked for guidance on model building as a hobby — scale models, kits, tools, and painting/finishing techniques for someone starting out.
Painting — Use when asked for guidance on painting as a hobby — choosing a medium (watercolor, acrylic, oil), basic materials, and technique fundamentals for someone starting out.
Photography — Use when asked for guidance on photography as a hobby — camera basics, composition, and light — for someone starting out or improving their craft.
Pottery — Use when asked for guidance on pottery/ceramics as a hobby — hand-building vs. the wheel, clay basics, and the firing process for someone starting out.
Quilting — Use when asked for guidance on quilting as a hobby — piecing, batting/backing basics, and choosing a manageable first project.
Rock Climbing — Use when asked for guidance on rock climbing as a hobby — starting at an indoor gym, basic safety systems, and building technique before moving outdoors.
Running — Use when asked for guidance on running as a recreational or fitness hobby — proper footwear, gradual progression, and injury-prevention basics for someone starting out.
Sewing — Use when asked for guidance on sewing as a hobby — machine basics, reading patterns, and starting a first project — covering both hand and machine sewing.
Video Gaming — Use when asked for guidance on video gaming as a hobby — choosing games/platforms, balancing time investment, and getting the most out of the hobby sustainably.
Woodworking — Use when asked for guidance on woodworking as a hobby — tools, wood selection, joinery basics, and shop safety for someone starting out.
Yoga — Use when asked for guidance on yoga as a hobby — choosing a style, building a beginner-safe practice, and the difference between flexibility and strength focus.

HR & compensation 7

Code of Conduct — Use when asked to write or revise a code of conduct — expected standards of behavior and ethics, reporting processes, and consequences for violations — distinct from the broader [[employee-handbook]], which covers practical policy across many topics rather than behavior and ethics specifically.
Compensation Benchmarking — Use when asked to compare an organization's pay against the external market — setting pay ranges, checking if an offer or raise is competitive, building a pay philosophy — distinct from [[job-description-with-uk-gdad-pcf-and-agenda-for-change]], a specific UK public-sector job-evaluation scheme rather than the general market-benchmarking practice covered here.
Employee Handbook — Use when asked to write or update an employee handbook — practical policies on time off, expenses, remote work, and how core processes work, plus required legal notices — distinct from a [[code-of-conduct]], which specifically defines expected behavior and ethics rather than covering practical policy across many topics.
Org Chart — Use when asked to build or update an org chart — a diagram of reporting lines and how roles or teams relate — including deciding what to name (roles vs. individuals), how to handle matrix or dotted-line relationships, and who owns keeping it current.
Salary Negotiation — Use when asked to prepare for or conduct a salary negotiation — the conversation over compensation for a specific job offer or role — as distinct from [[compensation-benchmarking]], the market-data research that informs what to actually ask for rather than the negotiation conversation itself.
Succession Planning — Use when asked to identify or develop people who could step into key roles if the current holder leaves — succession pipelines, readiness assessments, bench strength for critical positions — so a departure from a critical role doesn't create an operational crisis.
Total Rewards Statement — Use when asked to build or explain a total rewards statement — a document showing an employee the full value of their compensation package, including bonus, equity, and benefits, not just base salary — as distinct from a simple pay stub or offer letter that lists only cash pay.

Human languages 22

Arabic Language — Use when asked to write, translate into, or check text in Arabic — a right-to-left abjad script that normally omits short vowels, root-and-pattern morphology, and a major gap between Modern Standard Arabic and regional spoken dialects; official across the Middle East and North Africa with hundreds of millions of speakers.
Cymraeg Language — Use when asked to write, translate into, or check text in Cymraeg (Welsh) — a Celtic language with initial consonant mutations, digraphs treated as single alphabet letters, and grammatical gender — spoken mainly in Wales with official status alongside English.
Dutch Language — Use when asked to write, translate into, or check text in Dutch — the common/neuter gender system, verb-second word order in main clauses, the u/jij formal-informal distinction, and real vocabulary differences between Netherlandic and Flemish Dutch, official in the Netherlands, Belgium, and Suriname.
French Language — Use when asked to write, translate into, or check text in French — grammatical gender agreement, the vous/tu formal-informal and plural distinction, and liaison/elision conventions, official across France, Belgium, Switzerland, Canada, and many African countries.
Gaeilge Language — Use when asked to write, translate into, or check text in Gaeilge (Irish) — a Celtic language with initial mutations (lenition and eclipsis), the síneadh fada marking long vowels, and verb-subject-object word order — an official language of Ireland and of the EU, with a minority of first-language speakers.
Gaidhlig Language — Use when asked to write, translate into, or check text in Gàidhlig (Scottish Gaelic) — a Celtic language with lenition-style initial mutations, the grave accent marking long vowels, verb-subject-object word order, and a vocative case — spoken mainly in the Scottish Highlands and Islands with official recognition in Scotland.
German Language — Use when asked to write, translate into, or check text in German (Deutsch) — a Germanic language with a four-case noun system, grammatical gender that must be memorized per noun, and long compound nouns — official in Germany, Austria, and Switzerland, with real regional variation.
Hindi Language — Use when asked to write, translate into, or check text in Hindi — a Devanagari-script abugida with grammatical gender, postpositions instead of prepositions, and a three-tier second-person formality system; one of India's official languages at the union level, spoken natively by several hundred million people.
Indonesian Language — Use when asked to write, translate into, or check text in Indonesian (Bahasa Indonesia) — a Latin-script, phonetically regular language with no grammatical gender or tense inflection, reduplication for plurality, and productive prefix/suffix affixation; the official language of Indonesia, spoken by over 200 million people as a first or second language.
Italian Language — Use when asked to write, translate into, or check text in Italian — grammatical gender agreement, the tu/Lei formal-informal distinction (where Lei takes third-person verb forms), and a largely phonetic spelling system, official in Italy, Switzerland, San Marino, and Vatican City.
Japanese Language — Use when asked to write, translate into, or check text in Japanese (日本語) — the mixed kanji/hiragana/katakana writing system, the grammatically-encoded keigo honorific system, and subject-object-verb order with frequent subject omission — spoken mainly in Japan.
Korean Language — Use when asked to write, translate into, or check text in Korean (한국어) — the deliberately-designed Hangul alphabet, the honorific system (jondaetmal vs. banmal) encoded in verb endings, and South/North Korean vocabulary divergence — official in South Korea and North Korea.
Mandarin Chinese Language — Use when asked to write, translate into, or check text in Mandarin Chinese (普通话/國語) — Simplified vs. Traditional character choice, tone, and measure words (classifiers) instead of English-style plurals — the most widely spoken Chinese variety, official in mainland China, Taiwan, and Singapore.
Polish Language — Use when asked to write, translate into, or check text in Polish — the seven-case noun declension system, masculine-personal vs. non-masculine-personal gender agreement in the plural, diacritical letters (ą, ć, ę, ł, ń, ó, ś, ź, ż), and Pan/Pani third-person formal address, the official language of Poland.
Portuguese Language — Use when asked to write, translate into, or check text in Portuguese — grammatical gender agreement, the significant European-vs-Brazilian split in spelling/vocabulary/grammar, regionally variable formal-informal address (você, tu), and nasal vowels marked with a tilde, official in Portugal, Brazil, and several African and Asian countries.
Russian Language — Use when asked to write, translate into, or check text in Russian — a Cyrillic-script East Slavic language with a six-case noun system and grammatical verb aspect (perfective/imperfective); official in Russia and widely used across the former Soviet Union, spoken natively by well over 100 million people.
Scots Language — Use when asked to write, translate into, or check text in Scots — a Germanic language distinct from Scottish Gaelic, closely related to English but with its own core vocabulary, grammar, and multiple coexisting spelling conventions rather than one standard orthography — spoken in Lowland Scotland and, as Ulster Scots, in parts of Northern Ireland.
Spanish Language — Use when asked to write, translate into, or check text in Spanish — grammatical gender agreement, the tú/usted/vos formal-informal split, and inverted ¿¡ punctuation, spoken by roughly 500 million people as an official language across Spain and most of Latin America.
Swedish Language — Use when asked to write, translate into, or check text in Swedish (svenska) — a North Germanic language with a two-gender noun system, a definite article suffixed onto the noun, and pitch accent — official in Sweden and Finland, closely related to and largely mutually intelligible with Norwegian and Danish.
Thai Language — Use when asked to write, translate into, or check text in Thai (ภาษาไทย) — the abugida script written without spaces between words, five meaning-changing tones marked partly by tone rules rather than only tone marks, and a hierarchical pronoun/politeness-particle system that differs by speaker gender — official in Thailand.
Turkish Language — Use when asked to write, translate into, or check text in Turkish — a Latin-script agglutinative language with vowel harmony, a dotted/dotless I distinction that breaks naive text processing, and a formal/informal second person (siz/sen) split; official in Turkey and Cyprus, spoken natively by roughly 80 million people.
Vietnamese Language — Use when asked to write, translate into, or check text in Vietnamese (Tiếng Việt) — the heavily diacritic-marked Latin alphabet (Quốc Ngữ) with six meaning-changing tones, and a kinship-based pronoun system that encodes relative age and familiarity — official in Vietnam, with Northern, Central, and Southern regional variation.

IEEE 4

Ieee 1012 Software Verification and Validation — Use when asked to plan or assess verification and validation (V&V) of software using IEEE 1012, including V&V activities by life cycle stage, integrity levels, and independence. Distinct from [[ieee-730-software-quality-assurance]] (overall quality assurance), [[ieee-1028-software-reviews-and-audits]] (review procedures), and [[ieee-1061-software-quality-metrics]] (measurement).
Ieee 1028 Software Reviews and Audits — Use when asked to plan, run, or document a formal software review or audit under IEEE 1028, such as a management review, technical review, inspection, walk-through, or audit. Distinct from [[code-review-checklist]] (everyday code review), [[ieee-730-software-quality-assurance]] (SQA planning), and [[ieee-1012-software-verification-and-validation]] (V&V activities).
Ieee 1061 Software Quality Metrics — Use when asked to define software quality requirements and choose, collect, and validate software quality metrics using the IEEE 1061 methodology across the product life cycle. Distinct from [[software-engineering-metrics]] (general engineering measures), [[system-quality-attributes]] (non-functional requirements), and [[ieee-730-software-quality-assurance]] (SQA processes).
Ieee 730 Software Quality Assurance — Use when asked to plan, set up, or assess Software Quality Assurance (SQA) processes using IEEE 730, covering SQA planning, product and process assurance, and control across the life cycle. Distinct from [[ieee-1012-software-verification-and-validation]] (technical V&V activities), [[ieee-1028-software-reviews-and-audits]] (review and audit procedures), and [[ieee-1061-software-quality-metrics]] (measurement).

Information Technology Service Management 11

Agile Itil Guide — Use when asked to find, explain, or apply content from the Agile ITIL Guide, such as choosing topics for a role or problem, running a team conversation from a topic's discussion questions, or adapting one of its AI prompts to a team's own material. Companion to [[agile-itil-metrics]], which covers measurement; for the ITIL framework itself see [[itil-5]], for Agile values see [[agile-principles]], and for the wider service management guide see [[service-management-guide]].
Agile Itil Metrics — Use when someone asks how to measure an agile or ITIL practice (incidents, changes, flow, service levels, experience, assets, cost, risk, people, or AI), or needs the right topic, metric definition, gaming vector, guardrail, discussion question, or AI prompt from the Agile ITIL Metrics book. Companion to [[agile-itil-guide]], which covers the practices themselves; for the broader service management book see [[service-management-metrics]], and for general indicator design see [[key-performance-indicators]].
Cobit 2019 — Use when asked to apply COBIT 2019, the ISACA framework for enterprise IT governance and management, for risk management, regulatory compliance, cybersecurity, and corporate governance. Distinct from [[itil-5]] and [[iso-iec-20000]] (service management) and [[risk-register]] (a single risk tool).
Fitsm — Use when asked to set up lightweight IT service management with FitSM, a streamlined standard often described as "ITIL light", for small-to-medium organizations that want core process structure without heavy overhead. Distinct from [[itil-5]] (broader framework), [[iso-iec-20000]] (certifiable standard), and [[yasm]] (another simplified model).
Iso Iec 20000 — Use when asked about ISO/IEC 20000, the international standard for IT service management systems, including preparing for independent audit and certification for regulatory or procurement needs. Distinct from [[itil-5]] (guidance, not certifiable), [[fitsm]] (lightweight standard), and [[cobit-2019]] (governance framework).
Itil 5 — Use when asked to apply, explain, or adopt ITIL 5, the PeopleCert ITIL release that emphasizes digital product management and AI governance alongside service management. Distinct from [[iso-iec-20000]] (certifiable standard), [[verism]] (organization-wide approach), and [[product-management]] (general product practice).
Service Integration and Management — Use when asked to apply Service Integration and Management (SIAM), a methodology for managing multiple service suppliers in a complex ecosystem, especially when an organization outsources parts of IT and must integrate vendors. Distinct from [[vendor-management]] (single-supplier relationships), [[itil-5]], and [[service-level-agreement]].
Service Management Guide — Use when asked to find, explain, or apply content from the Service Management Guide, such as choosing topics for a role or problem, running a team conversation from a topic's discussion questions, adapting one of its AI prompts to a team's own material, or looking at a practice through agile, AI, automation, and analytics. Companion to [[service-management-metrics]], which covers measurement; for frameworks and standards see [[itil-5]], [[iso-iec-20000]], and [[fitsm]], and for the agile variant see [[agile-itil-guide]].
Service Management Metrics — Use when someone asks how to measure a service management practice (incidents, changes, flow, service levels, experience, assets, cost, risk, people, or AI), or needs the right topic, metric definition, gaming vector, guardrail, discussion question, or AI prompt from the Service Management Metrics book. Companion to [[service-management-guide]], which covers the practices themselves; for the agile variant see [[agile-itil-metrics]], for service level agreements see [[service-level-agreement]], and for general indicator design see [[key-performance-indicators]].
Verism — Use when asked to apply VeriSM, an organization-level approach to service management that combines several management practices (such as Agile, DevOps, Lean, and ITIL) across the whole business. Distinct from [[itil-5]] (one framework), [[agile-principles]] (one practice), and [[cobit-2019]] (governance framework).
Yasm — Use when asked to adopt YaSM, a simplified, streamlined service management model with a pre-defined process framework that is quick to adopt. Distinct from [[fitsm]] (a lightweight standard), [[itil-5]] (fuller framework), and [[iso-iec-20000]] (certifiable standard).

Legal skills 24

Legal Arbitration and Mediation — Use when asked about arbitration or mediation — structured alternative dispute resolution processes outside court — as faster, more private alternatives to litigation, with arbitration producing a binding decision and mediation facilitating a negotiated settlement.
Legal Brief Writing — Use when asked to write a legal brief — a persuasive written argument presenting facts, legal issues, and analysis to a court or decision-maker — building on legal-research's findings into a structured, persuasive document.
Legal Case Management — Use when asked about legal case (matter) management — tracking deadlines, documents, communications, and status across a legal matter from intake to resolution — the organizational backbone connecting most other legal-practice skills.
Legal Cease and Desist Letter — Use when asked to write or explain a cease-and-desist letter — formally demanding that a party stop specific unlawful or infringing conduct — as a common first step before formal litigation.
Legal Client Engagement Letter — Use when asked to write or explain a legal client engagement letter — formally defining the scope, fees, and terms of a lawyer-client representation — following a legal-conflict-of-interest-check.
Legal Compliance Audit — Use when asked to conduct a legal compliance audit — systematically checking an organization's actual practices against applicable laws and regulations — as an internal, ongoing counterpart to legal-due-diligence's transaction-specific investigation.
Legal Conflict of Interest Check — Use when asked about legal conflict-of-interest checks — verifying a lawyer or firm can ethically represent a client given current and former relationships — a required step before accepting representation.
Legal Contract Drafting — Use when asked to draft a contract from scratch — structuring clauses, defining terms precisely, and anticipating what could go wrong — as the drafting-side counterpart to contract-review's reviewing-side focus, feeding into legal-contract-negotiation.
Legal Contract Negotiation — Use when asked to negotiate contract terms between parties — identifying priorities, trading concessions, and reaching an agreement both sides will actually honor — building on legal-contract-drafting and contract-review.
Legal Corporate Governance — Use when asked about corporate governance from a legal perspective — board duties, shareholder rights, and the legal structures that govern how a company is directed and controlled — distinct from general management-discipline concepts.
Legal Data Privacy Compliance — Use when asked about legal data privacy compliance — meeting obligations under data protection laws (such as GDPR, CCPA, and similar regimes) for collecting, using, and protecting personal data — as a specific, commonly audited compliance area.
Legal Deposition Preparation — Use when asked to prepare a witness for a deposition — sworn, out-of-court testimony taken during discovery — covering what to expect, how to answer, and common mistakes to avoid.
Legal Discovery Request — Use when asked about discovery requests in litigation — formally requesting documents, information, or testimony from an opposing party — as the formal information-exchange process that follows a legal-litigation-hold.
Legal Due Diligence — Use when asked to conduct legal due diligence — systematically investigating a counterparty's legal, financial, and contractual standing before a transaction (M&A, investment, major contract) — distinct from legal-research's narrower legal-question focus.
Legal Intellectual Property Filing — Use when asked about filing intellectual property protections — patents, trademarks, copyrights — as the general IP-filing overview that legal-trademark-registration and legal-patent-application specialize.
Legal Litigation Hold — Use when asked about a litigation hold (legal hold) — the obligation to preserve potentially relevant documents and data once litigation is reasonably anticipated — as the trigger event that precedes legal-discovery-request and legal-e-discovery.
Legal Merger and Acquisition Review — Use when asked about the legal review process for a merger or acquisition — structuring the deal, due diligence, regulatory approval, and closing — building on legal-due-diligence and legal-corporate-governance.
Legal Patent Application — Use when asked about the patent application process — novelty searching, drafting claims, and prosecution — as a specialization of legal-intellectual-property-filing, protecting inventions rather than brand identifiers.
Legal Regulatory Filing — Use when asked about regulatory filings — submitting required disclosures, applications, or reports to a government regulator — as the general regulatory-submission process underlying more specific filings.
Legal Research — Use when asked to conduct legal research — finding and analyzing statutes, case law, and regulations to answer a legal question — as the foundational skill underlying legal-brief-writing and most other legal-practice work in this collection.
Legal Risk Assessment — Use when asked to assess legal risk — identifying, evaluating, and prioritizing an organization's exposure to legal liability, regulatory action, or dispute — as the framework that turns legal-due-diligence and legal-compliance-audit findings into prioritized action.
Legal Settlement Negotiation — Use when asked to negotiate a legal settlement — resolving a dispute or claim without (or before) trial — as a specialized application of legal-contract-negotiation to the litigation/dispute context.
Legal Trademark Registration — Use when asked about the trademark registration process — clearance searching, filing, and use requirements for protecting a brand identifier — as a specialization of legal-intellectual-property-filing.
Legal Whistleblower Complaint Handling — Use when asked about handling a whistleblower complaint — receiving, investigating, and protecting an employee who reports suspected wrongdoing — including anti-retaliation obligations, as a specific, sensitive compliance process.

Legal › Contracts 12

Contract Review — Use when asked to review a contract before signing, or to build a contract-review checklist — covering scope, payment, termination, liability, confidentiality, and renewal terms — as a general review practice rather than a specific type of contract; for general guidance only, not legal advice, so always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
Estate Planning — Use when asked to plan or explain estate planning — the broader practice of arranging how a person's assets and affairs will be handled during incapacity and after death, of which a will and a power of attorney are two specific component documents — for general guidance only, not legal advice; always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
Last Will and Testament — Use when asked to draft, review, or explain a last will and testament — a legal document stating how a person's assets should be distributed after death and naming an executor to carry that out — for general guidance only, not legal advice; always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
Lease Agreement — Use when asked to draft, review, or explain a lease agreement — a legal contract between a landlord and tenant setting the terms for renting property — for general guidance only, not legal advice; always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
Non-Disclosure Agreement — Use when asked to draft, review, or explain a non-disclosure agreement (NDA) — a legal agreement protecting confidential information shared between parties, mutual or one-way — for general guidance only, not legal advice; always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
Power of Attorney — Use when asked to draft, review, or explain a power of attorney — a legal document authorizing someone (the agent, or attorney-in-fact) to act on another person's (the principal's) behalf for financial, legal, or medical decisions — for general guidance only, not legal advice; always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
Privacy Policy — Use when asked to draft or review a privacy policy — the legal disclosure of what personal data a product collects, why, and how it's handled — for general guidance only, not legal advice; always direct the reader to consult a qualified lawyer for their specific situation, jurisdiction, and regulatory obligations (e.g. GDPR, CCPA). Distinct from a [[terms-of-service]], which governs usage rights and conduct rather than data handling.
Property Management — Use when asked about the ongoing operational management of a rental property or portfolio on behalf of an owner — rent collection, maintenance, tenant communication, inspections — distinct from a [[lease-agreement]], which is the contract with one tenant, where this is the ongoing operational practice across the property's lifecycle and possibly multiple units and tenants.
Request for Proposal — Use when asked to write a request for proposal (RFP) — a procurement document soliciting competing bids from vendors for a defined need — as distinct from a [[statement-of-work]], which defines what the vendor actually selected will deliver, usually written after the RFP process ends.
Service Level Agreement — Use when asked to draft or review a service level agreement (SLA) — defining expected service performance such as uptime, response time, or support tiers between a provider and customer — as distinct from a statement-of-work, which defines a project's specific deliverables and scope rather than ongoing performance standards; for general guidance only, not legal advice, so always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction.
Terms of Service — Use when asked to draft or review terms of service (ToS) — the legal agreement governing how users may use a product or service — for general guidance only, not legal advice; always direct the reader to consult a qualified lawyer for their specific situation and jurisdiction. Distinct from a [[privacy-policy]], which governs data handling rather than usage rights and conduct.
Vendor Management — Use when asked to set up or run ongoing vendor management — the practice of overseeing an external vendor relationship after a contract is signed — as distinct from the earlier selection stage covered by [[request-for-proposal]] and [[contract-review]].

Lily Design System 8

Lily Design System Angular — Use when someone asks what's available for Angular in Lily Design System, which Angular subproject they need (the headless component library, the six *-picker helpers, or the styled example app), wants to see Lily's Angular components running with real CSS, or asks about the Angular Analog.js example app's routes, NHS UK visual reference, or composed-page demos.
Lily Design System Blazor — Explains what's available for Blazor in Lily Design System and which of the three real Blazor subprojects an agent needs — the headless component library (the NuGet package you depend on and style yourself), the six *-picker helpers catalog (opinionated, whole-interaction packages for a page-header preference/action or a form control), or the Blazor Web example app (a fully NHS-UK-styled reference you can run to see components working, or copy CSS from). Use when someone asks what Lily offers for Blazor, which Blazor package to install for a given job, how to run the Blazor example app, or wants Blazor Web App hosting-model guidance (Server / WebAssembly / static SSR).
Lily Design System HTML — Explains what's available for plain HTML in Lily Design System and helps decide which of the three real HTML subprojects to reach for — the full-catalog headless component library, the six *-picker helper web components, or the styled NHS UK example application. Use when someone asks what Lily offers for plain/vanilla HTML with no framework, which HTML subproject they need, how the HTML headless library relates to the HTML helpers catalog or the example app, wants to see Lily components styled and running with no framework runtime, or asks how the plain-HTML catalogs differ from the separate Web Components catalogs.
Lily Design System Nunjucks — Umbrella skill for Nunjucks in Lily Design System — explains which of the three real Nunjucks subprojects to reach for (the 491-component headless macro library, the six *-picker helper packages, or the fully styled Eleventy example app), points to the two deeper sibling skills for the headless and helpers contracts, and gives real coverage of the Eleventy example app that neither sibling skill covers. Use when someone asks what's available for Nunjucks in Lily Design System, which Nunjucks subproject or package they need, how the three Nunjucks pieces relate, or wants to run or copy CSS from the styled Nunjucks/Eleventy reference app.
Lily Design System React — Explains what's available for React in Lily Design System and which of the three real React subprojects to reach for — the headless component library, the six *-picker helpers, or the Next.js example app. Use when someone asks what React support Lily Design System has, which React package they need, wants to see Lily's React components styled and running, or asks about the Next.js example app's routes, NHS UK styling, or App Router setup.
Lily Design System Svelte — Explains what's available for Svelte in Lily Design System and which Svelte subproject to reach for — the headless component library, the canonical *-picker helpers catalog (every other framework ports from this one), or the SvelteKit example application. Use when someone asks what Svelte packages Lily ships, which Svelte subproject they need for a given job, wants to see Svelte components styled and running, or asks about the SvelteKit example app's routes, NHS UK styling, or test coverage.
Lily Design System Vue — Use when someone asks what's available for Vue in Lily Design System, which Vue subproject they need (the headless component library, the *-picker helpers catalog, or the Nuxt.js example app), wants to run or see Vue components styled and working end-to-end, or needs the Nuxt-specific example app's routes and conventions before either sibling skill applies.
Lily Design System Web Components — Explains what's available as native Web Components in Lily Design System and which of the two real Web Components subprojects to reach for — the partial (33/491) headless custom-element catalog, or the six `<lily-*-picker>` helpers catalog. Use when someone asks what Lily offers as native Web Components, which Web Components subproject they need, how the Web Components headless catalog relates to the Web Components helpers catalog, or asks whether there's a Web Components example application (there isn't one yet).

Management disciplines 22

Critical Chain — Use when asked to explain or apply Critical Chain Project Management (CCPM) — resource-constrained scheduling, project/feeding buffers, or why CCPM removes individual task-level safety margins — as distinct from the Critical Path Method (see critical-path).
Critical Path — Use when asked to compute or explain a project's critical path — the Critical Path Method (CPM), forward/backward pass, float/slack — as distinct from Critical Chain Project Management's resource-buffer approach (see critical-chain).
Feature Prioritization — Use when asked to rank competing feature or work candidates — via RICE, MoSCoW, value-vs-effort, or a similar framework — instead of prioritizing by whoever argues loudest or whichever request came in most recently.
Functional Specification — Use when asked to write a functional specification — user interface descriptions, inputs/outputs, technical details, error handling — as the detailed requirements document a project-scope's requirements section points to, and the source of truth acceptance-testing checks delivered software against.
Portfolio Management — Use when asked to prioritize an organization's whole set of projects/programs against strategy and capacity, write a portfolio review or investment case, or explain portfolio management concepts (strategic alignment, capacity-based sequencing) — as distinct from managing one project (see project-management) or one program of related projects (see program-management).
Practice Management — Use when asked how to run a professional practice — either a discipline-based community of practice inside a larger organization (e.g. a UX practice, an engineering practice) or a client-facing professional practice (legal, medical, consulting) — covering practice standards, capability development, and utilization/workload management. Distinct from managing one project or program (see project-management, program-management).
PRINCE2 — Use when asked about PRINCE2 (Projects IN Controlled Environments) — its process-based, product-based-planning, business-justification-driven approach — as a structured, phase-gated methodology contrasted with agile/Scrum (see scrum, agile-principles) rather than a replacement for project-management's general concepts.
Product Management — Use when asked to write a product strategy/roadmap, prioritize a backlog, define OKRs or success metrics for a product, or explain product-management concepts (discovery vs delivery, prioritization frameworks) — as distinct from project management (see project-management) or program/portfolio management (see program-management, portfolio-management).
Product Requirements Document — Use when asked to write or review a Product Requirements Document (PRD) — what a feature or product should do and why, before it's built — distinct from a [[functional-specification]] (broader technical scope of how it's built) and a [[user-story]] (one specific PRD requirement written from the user's perspective, typically one of several inside a PRD).
Product Roadmap — Use when asked to build, review, or explain a product roadmap — the ongoing, product-wide plan of themes and rough timeframes communicated to stakeholders — distinct from a [[project-charter]], which is a single project's formal scope document with a defined start and end.
Program Management — Use when asked to coordinate multiple related projects toward one business outcome, write a program charter/benefits map, or explain program management concepts (benefits realization, cross-project dependency management) — as distinct from managing a single project (see project-management) or an organization's whole investment set (see portfolio-management).
Project Charter — Use when asked to write a formal project charter — purpose, scope, objectives, deliverables, stakeholders, assumptions, risks, budget, and schedule — as distinct from a collaborative agile chartering session (see agile-charter), which co-creates alignment rather than producing an approved document.
Project Management — Use when asked to plan a project, write a project charter/status update/RAID log, choose between waterfall/agile/hybrid delivery, or explain project-management concepts (scope/schedule/cost triangle, critical path, risk register, stakeholder management) — independent of any specific methodology certification (PMP, PRINCE2) or tool.
Project Management Body of Knowledge — Use when asked about PMBOK (the Project Management Body of Knowledge, published by PMI) specifically — its knowledge areas and process groups — as distinct from the general project-management discipline and from a specific methodology like prince2.
Project Scope — Use when asked to define or control a project's scope — objectives, deliverables, requirements, assumptions/constraints — as the boundary-setting discipline a project-charter document formalizes and a work-breakdown-structure decomposes into executable work.
RACI Matrix — Use when asked to build a RACI matrix specifically — the Responsible/Accountable/Consulted/Informed variant of responsibility-assignment-matrix — including the PARIS variant sometimes used instead.
Responsibility Assignment Matrix — Use when asked to build a Responsibility Assignment Matrix (RAM) — a grid mapping team members to tasks with a responsibility level in each cell — as the general umbrella concept behind named variants like raci-matrix, RACIO, and PARIS.
Risk Register — Use when asked to create or maintain a risk register — a living table of identified risks with likelihood, impact, score, owner, mitigation, and status — as distinct from a full RAID log ([[risks-actions-issues-decisions]]), which also tracks actions, issues, and decisions, and from [[key-risk-indicators]], which are the metrics that signal a risk is materializing.
Risks Actions Issues Decisions — Use when asked to maintain a RAID log using the Risks/Actions/Issues/Decisions expansion of RAID — one of two common RAID acronym expansions in project management, the other being Risks/Assumptions/Issues/Dependencies (see project-management). Confirm which expansion a specific team means before assuming.
Statement of Work — Use when asked to write or structure a Statement of Work (SOW) — abstract/scope/payment sections, objectives via OKRs, performance via KPIs, or a RACI-style responsibility matrix — grounded in joelparkerhenderson/statement-of-work, as distinct from a full contract's legal terms.
User Story — Use when asked to write or review a user story — a short, structured statement of a specific end-user need ("As a [role], I want [goal], so that [benefit]") that drives a feature — typically one of several components inside a larger [[product-requirements-document]].
Work Breakdown Structure — Use when asked to build a Work Breakdown Structure (WBS) — hierarchically decomposing a project's deliverables into manageable work packages — as the concrete decomposition of an agreed project-scope boundary, feeding critical-path's schedule analysis and task assignment.

Marketing & content 13

Brand Style Guide — Use when asked to build a brand style guide — a reference document defining how a brand looks and sounds across every touchpoint, covering visual identity, voice and tone, and usage rules — distinct from [[branding]], the broader strategic work of defining what the brand actually is, which the style guide codifies into something teams can apply day to day.
Competitor Analysis — Use when asked to build a competitor analysis — a structured, side-by-side comparison of a company or product against named competitors on the dimensions buyers actually care about — distinct from a [[five-forces-analysis]] (industry-wide competitive forces) and a [[swot-analysis]] (one company's own strengths, weaknesses, opportunities, and threats), neither of which names specific alternatives and compares against them directly.
Content Calendar — Use when asked to build or maintain a content calendar — a scheduled plan of what content gets published on which channel and when, with an owner and status per item — distinct from a [[press-release]] or any single piece of content, which is one entry that might sit on the calendar rather than the schedule itself.
Customer Journey Map — Use when asked to build a customer journey map — a visual map of the stages a customer goes through with a product or service, from awareness to advocacy, including their thoughts, feelings, and friction at each stage — distinct from a [[customer-persona]], which describes who the customer is rather than what they actually go through.
Customer Persona — Use when asked to build a customer persona — a composite profile of a customer segment, covering goals, pain points, and behavior, used to guide product and marketing decisions — distinct from a [[customer-journey-map]], which maps what that customer actually goes through rather than who they are.
Press Release — Use when asked to write a press release — a formal announcement of company news (a launch, funding round, partnership, or milestone) written for media pickup — distinct from [[release-notes]] or a [[changelog]], which announce product changes to existing users rather than pitch a story to journalists.
Share on Bluesky — Use when asked to write a Bluesky post (≤300 characters) announcing a personal project to busy professionals — generating interest, asking for help/advice, and inviting shares in a humble, personal voice — as distinct from [[share-on-facebook]], [[share-on-instagram]], [[share-on-linkedin]], [[share-on-mastodon]], and [[share-on-threads]] (same announcement, different platform conventions), or [[press-release]] and [[copywriting]] (formal/persuasive registers this deliberately avoids).
Share on Facebook — Use when asked to write a Facebook post (personal profile or Group, effectively unlimited length but written short) announcing a personal project to busy professionals — generating interest, asking for help/advice, and inviting shares in a humble, personal voice — as distinct from [[share-on-bluesky]], [[share-on-instagram]], [[share-on-linkedin]], [[share-on-mastodon]], and [[share-on-threads]] (same announcement, different platform conventions), or [[press-release]] and [[copywriting]] (formal/persuasive registers this deliberately avoids).
Share on Instagram — Use when asked to write an Instagram caption (≤2200 characters) announcing a personal project to busy professionals — generating interest, asking for help/advice, and inviting shares in a humble, personal voice — as distinct from [[share-on-bluesky]], [[share-on-facebook]], [[share-on-linkedin]], [[share-on-mastodon]], and [[share-on-threads]] (same announcement, different platform conventions), or [[press-release]] and [[copywriting]] (formal/persuasive registers this deliberately avoids).
Share on Linkedin — Use when asked to write a LinkedIn post (≤3000 characters) announcing a personal project to busy professionals — generating interest, asking for help/advice, and inviting shares in a humble, personal voice — as distinct from [[share-on-linkedin-projects]] (a static profile entry, not a feed post) and [[share-on-bluesky]], [[share-on-facebook]], [[share-on-instagram]], [[share-on-mastodon]], and [[share-on-threads]] (same announcement, different platform conventions), or [[press-release]] and [[copywriting]] (formal/persuasive registers this deliberately avoids).
Share on Linkedin Projects — Use when asked to write a LinkedIn profile Projects section entry (title + description, ) showcasing a personal project to busy professionals — generating interest, asking for help/advice, and inviting shares in a humble, personal voice — as distinct from [[share-on-linkedin]] (a feed post: algorithmically ranked, time-bound, reached mainly by followers and their networks) and [[share-on-bluesky]], [[share-on-facebook]], [[share-on-instagram]], [[share-on-mastodon]], and [[share-on-threads]] (feed posts on other platforms), or [[press-release]] and [[copywriting]] (formal/persuasive registers this deliberately avoids).
Share on Mastodon — Use when asked to write a Mastodon post (≤500 characters, the common instance default) announcing a personal project to busy professionals — generating interest, asking for help/advice, and inviting shares in a humble, personal voice — as distinct from [[share-on-bluesky]], [[share-on-facebook]], [[share-on-instagram]], [[share-on-linkedin]], and [[share-on-threads]] (same announcement, different platform conventions), or [[press-release]] and [[copywriting]] (formal/persuasive registers this deliberately avoids).
Share on Threads — Use when asked to write a Threads post (≤500 characters) announcing a personal project to busy professionals — generating interest, asking for help/advice, and inviting shares in a humble, personal voice — as distinct from [[share-on-bluesky]], [[share-on-facebook]], [[share-on-instagram]], [[share-on-linkedin]], and [[share-on-mastodon]] (same announcement, different platform conventions), or [[press-release]] and [[copywriting]] (formal/persuasive registers this deliberately avoids).

Medical › Communication 5

Medical Family Conference — Use when asked to structure or prepare for a family conference — a structured conversation between the clinical team and a patient's family (sometimes including the patient) about goals of care, prognosis, or a major treatment decision — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Morbidity and Mortality Review — Use when asked to structure or prepare a morbidity and mortality (M&M) review — a recurring, blameless peer-review conference examining a case with a poor outcome or complication to identify systemic learning — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Multidisciplinary Team Meeting — Use when asked to structure, prepare for, or run a multidisciplinary team (MDT) meeting — a structured meeting bringing together clinicians from different disciplines to coordinate a patient's care plan — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical SBAR Handoff — Use when asked to structure, write, or review an SBAR (Situation, Background, Assessment, Recommendation) clinical handoff — a single-patient communication such as nurse-to-physician or between shifts about one concerning patient — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Shift Handoff Report — Use when asked to structure, write, or review a shift handoff report — the systematic handoff of a full patient list/assignment from one shift's clinical team to the next — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.

Medical › Documentation 6

Medical Admission Note — Use when asked to write, review, or structure a hospital admission note — the comprehensive note documenting a patient's condition and plan at the point of admission — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Discharge Summary — Use when asked to write, review, or structure a hospital discharge summary — the document summarizing a hospital stay for the clinician who picks up care afterward — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Medication Reconciliation — Use when asked to perform, document, or structure medication reconciliation — comparing a patient's actual current medications against what's documented at a care transition to catch discrepancies — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Nursing Care Plan — Use when asked to write, review, or structure a formal nursing care plan — the clinical nursing document identifying nursing diagnoses, measurable goals, planned interventions, and evaluation — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Referral Letter — Use when asked to write, review, or structure a clinical referral letter — a letter from one clinician to another requesting evaluation or care of a patient — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical SOAP Note — Use when asked to write, review, or structure a SOAP note — the Subjective, Objective, Assessment, Plan format for a clinical progress note documenting a patient encounter — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.

Medical › Protocols 5

Medical Early Warning Score — Use when asked to administer, score, or explain an early warning score — using NEWS2 (National Early Warning Score 2) as the primary example — a bedside physiological scoring system that prompts escalation before a crisis develops, for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Fall Prevention Protocol — Use when asked to describe or implement a fall prevention protocol — the bundle of interventions put in place once a patient screens as at-risk via a fall risk assessment — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Hand Hygiene Compliance — Use when asked to describe, implement, or audit a hand hygiene compliance program — defined hand hygiene moments, direct observation, and feedback to staff — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Infection Control Protocol — Use when asked to describe, implement, or audit a facility infection control protocol — standard precautions plus transmission-based precautions, environmental cleaning, and compliance monitoring — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Pressure Injury Prevention — Use when asked to describe or implement a pressure injury (bedsore) prevention protocol — the bundle of repositioning, skin checks, and pressure-redistributing equipment applied once a patient screens as at-risk — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.

Medical › Quality & safety 6

Medical Adverse Event Review — Use when asked to structure, conduct, or write up an adverse event review — a structured investigation into a serious patient-safety event to identify contributing systemic factors — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Clinical Audit — Use when asked to design, run, or explain a clinical audit — a systematic review of clinical practice against a defined standard to measure and improve quality — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Clinical Incident Report — Use when asked to file, structure, or review a clinical incident report — the factual account filed when a patient-safety incident or near-harm event occurs — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Medication Error Reporting — Use when asked to structure or explain the medication error reporting process — including near-misses that never reached the patient — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
Medical Patient Safety Huddle — Use when asked to structure or run a patient safety huddle — a brief, regular team meeting focused specifically on patient-safety risks for the current period — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.
United Kingdom National Health Service Digital Technology Assessment Criteria — Use when asked to complete, review, or prepare evidence for the UK NHS Digital Technology Assessment Criteria (DTAC) form v2.0 — the baseline questionnaire a digital health technology manufacturer gives to NHS and social care buyers, covering company information, value proposition, clinical safety (DCB0129), data protection, technical security, interoperability, and usability and accessibility — or to check a supplier's DTAC answers as a buyer. Distinct from [[medical-clinical-audit]] (auditing care delivery), [[accessibility-testing]] (the WCAG testing that feeds section D1), and [[penetration-testing]] (the test that feeds section C3).

Meetings 8

All Hands Meeting — Use when asked to plan or run an all-hands (town hall) meeting — company-wide updates, Q&A, culture-building — as distinct from a one-on-one (see one-on-one-meeting) or skip-level meeting (see skip-level-meeting), which involve a small number of participants rather than the whole organization.
Meeting Agenda — Use when asked to write a meeting agenda — the pre-meeting document listing what will be covered, in what order, with how much time and who owns each item — as the generic agenda-writing craft behind specific meeting formats like [[one-on-one-meeting]], [[all-hands-meeting]], and [[weekly-planning-meeting]].
Meeting Minutes — Use when asked to write meeting minutes — the after-the-fact record of what was discussed, decided, and assigned in a meeting — as distinct from a [[meeting-agenda]], which is the before-the-meeting plan rather than the after-the-meeting record.
One on One Meeting — Use when asked to plan or run a regular one-on-one between a manager and a direct report — agenda, preparation, feedback, follow-up — as distinct from a skip-level meeting (see skip-level-meeting), which deliberately involves a non-direct-report relationship instead.
Performance Review Meeting — Use when asked to plan or run a formal performance review meeting — evaluating an employee's work against expectations over a defined period — as distinct from a regular one-on-one's ongoing, informal check-ins (see one-on-one-meeting), which should mean nothing in a performance review comes as a surprise.
Skip Level Meeting — Use when asked to plan or run a skip-level meeting — a leader meeting with employees below their direct reports — as distinct from a regular one-on-one (see one-on-one-meeting), and specifically requiring careful follow-up with the skipped manager to avoid undermining them.
Weekly Planning Meeting — Use when asked to plan or run a weekly team planning meeting — reviewing last week's progress and committing to this week's priorities — as the short-cycle execution counterpart to yearly-planning-meeting's annual strategy setting, and distinct from a daily standup's much shorter, status-focused check-in (see agile-standup).
Yearly Planning Meeting — Use when asked to plan or run an annual planning meeting — setting the organization's yearly strategy, budget, and top-level objectives — as the longest-horizon planning cadence in this collection, feeding weekly-planning-meeting's shorter execution cycle and drawing on vision-mission-values and strategic-balanced-scorecard.

Nonprofits 8

Donor Management — Use when asked to build or improve how an organization tracks and nurtures relationships with its donors — giving history, stewardship, segmentation — as the ongoing relationship practice distinct from a one-time [[grant-proposal]] submitted to a specific funder.
Fundraising Event Planning — Use when asked to plan a revenue-generating event — a gala, auction, or walkathon with a fundraising target — as distinct from `event-planning`, which has no revenue goal, and [[grant-proposal]], which is a written ask to one institutional funder rather than a ticketed public event.
Grant Proposal — Use when asked to write a grant proposal — a formal application requesting funding from a foundation, government body, or other grantmaker for a specific project or program, covering need, objectives, budget, and evaluation — as distinct from the ongoing relationship work of [[donor-management]] with individual donors.
Membership Program Design — Use when asked to design a recurring-revenue membership program — tiers, benefits, renewal cadence — for a nonprofit or association, as distinct from [[donor-management]], which covers major or one-time gift relationships rather than a structured tiered product, and [[fundraising-event-planning]], which raises one-time event revenue rather than recurring dues.
Nonprofit Board Governance — Use when asked about the roles, fiduciary duties, and committee structure of a volunteer nonprofit board — as distinct from `legal-corporate-governance`, which covers for-profit corporate boards, and from `board-deck`, which is a presentation artifact a board reviews rather than the governance structure itself.
Nonprofit Impact Report — Use when asked to report an organization's outcomes and impact to funders, the board, or the public after work has happened — as distinct from [[grant-proposal]], which asks for money before the work happens, and [[donor-management]], which is ongoing relationship tracking rather than a formal report artifact.
Nonprofit Strategic Plan — Use when asked to build a mission-driven, multi-year strategic plan for a nonprofit — theory of change, mission alignment, impact-tied goals — as distinct from a for-profit strategic plan, which is organized around revenue and market share rather than mission and impact.
Volunteer Management — Use when asked to build or improve how an organization recruits, screens, schedules, and retains unpaid volunteers — as distinct from [[donor-management]], which tracks people who give money rather than time, and from `employee-onboarding`, which covers paid staff.

Organizations 6

Community of Practice — Use when asked to build or run a Community of Practice (CoP) — an informal, cross-team knowledge-sharing group organized around a shared discipline — as the "internal community" sense of practice-management's dual meaning, distinct from a formal reporting structure.
Continuing Professional Development — Use when asked to plan or evidence continuing professional development (CPD) — a CPD log/portfolio, reflective practice, or setting individual development goals — as an individual practitioner activity, as distinct from the organizational People & OD function that supports it (see people-and-organizational-development) or a specific framework's own CPD checklist (see united-kingdom-government-digital-and-data-profession-capability-framework for one real example).
Organizational Development — Helps someone use this repository's organizational development (OD) guide to diagnose a real workplace problem and pick the right framework — a diagnostic model, change model, culture model, or intervention — with its evidence strength, use-when/do-not-use-when boundaries, and a worked example for their audience (health care, software, or executive). Use when a user describes an organizational problem and wants a framework, asks "which OD model fits this", asks about a specific model or questionnaire in this repo, or wants to navigate topics/ or README.md.
People and Organizational Development — Use when asked about the People & OD function as an organizational role — workforce planning, talent management, learning & development, or org design responsibilities — as distinct from the organizational-development's specific diagnostic models/frameworks, which this function is often the one applying.
United Kingdom Government Digital and Data Profession Capability Framework — Use this skill when someone wants to use the published UK GDAD PCF content — find a role level in the UK Government Digital and Data Profession Capability Framework, read its documents, rate their own skills, or plan their development. Triggers on questions like "what does a senior data analyst need to know", "find my role in the GDAD framework", "help me self-assess against a role level", "what should I learn for X role", or any mention of the UK GDAD PCF, ddat-capability-framework, or uk-gdad.github.io as something to use rather than edit.
Ways of Working — Use when asked to write or improve a team's ways of working — ground rules, working agreements, meeting/communication/feedback norms, remote/async practices, or onboarding/orientation docs — or to distinguish "principles" from "values", "tenets", "norms", and "working agreements" when a team is documenting how it operates.

Productivity tools 4

Event Planning — Use when asked to plan a one-off event — a party, offsite, conference, or wedding-adjacent gathering — covering guest list, venue, date, budget, and day-of run-of-show, as distinct from [[travel-itinerary]], which applies similar day-of logistics discipline to a trip rather than an event.
Home Inspection Checklist — Use when asked to build or work through a home inspection checklist — a systematic check of a home's condition, typically before a purchase, though the same discipline applies before signing a [[lease-agreement]] or before a move via [[moving-checklist]] — not to be confused with either of those, which cover the contract and the move itself rather than the property's physical condition.
Moving Checklist — Use when asked to plan or track a move to a new home — notifying landlords and utilities, booking movers, packing, and updating your address afterward — as a personal relocation checklist rather than a business or project-management artifact.
Travel Itinerary — Use when asked to build a travel itinerary — a day-by-day schedule of transport, lodging, activities, and confirmations for a trip — whether from scratch, from a list of bookings, or by organizing scattered confirmation emails into one usable document.

Productivity tools › Microsoft Office 4

Microsoft Excel — Use when asked about Microsoft Excel specifically — formulas and functions, tables, PivotTables, charts, conditional formatting, Office Scripts/VBA automation — as distinct from the general microsoft-office suite overview and from google-sheets, its closest Google Workspace equivalent.
Microsoft Office — Use when asked about Microsoft Office as a suite — how Word, Excel, PowerPoint, and related apps fit together, file formats (.docx/.xlsx/.pptx), shared features (co-authoring, templates, Office Scripts/VBA automation) — for app-specific detail see microsoft-word, microsoft-excel, and microsoft-powerpoint.
Microsoft Powerpoint — Use when asked about Microsoft PowerPoint specifically — slide masters/layouts, animations and transitions, speaker notes, Designer — as distinct from the general microsoft-office suite overview and from google-slides, its closest Google Workspace equivalent, and from pitch-deck for the content/structure of a pitch specifically.
Microsoft Word — Use when asked about Microsoft Word specifically — styles, templates, track changes/comments, mail merge, references/citations — as distinct from the general microsoft-office suite overview and from google-docs, its closest Google Workspace equivalent.

Productivity tools › Google Workspace 4

Google Docs — Use when asked about Google Docs specifically — styles, real-time co-editing, suggesting mode, comments, version history — as distinct from the general google-drive suite overview and from microsoft-word, its closest Microsoft Office equivalent.
Google Drive — Use when asked about Google Drive/Workspace as a suite — how Docs, Sheets, and Slides fit together, cloud-native storage and sharing, real-time collaboration — for app-specific detail see google-docs, google-sheets, and google-slides; the Google Workspace counterpart to microsoft-office.
Google Sheets — Use when asked about Google Sheets specifically — formulas and functions, pivot tables, conditional formatting, Apps Script automation, connected sheets/data connectors — as distinct from the general google-drive suite overview and from microsoft-excel, its closest Microsoft Office equivalent.
Google Slides — Use when asked about Google Slides specifically — themes/layouts, real-time co-editing, speaker notes, transitions — as distinct from the general google-drive suite overview and from microsoft-powerpoint, its closest Microsoft Office equivalent, and from pitch-deck for the content/structure of a pitch specifically.

Productivity tools › OpenDocument 6

Open Document Database — Use when asked about OpenDocument Database (`.odb`) files — the ISO/IEC 26300 database-document format that either embeds a database engine or merely stores connection settings/forms/reports pointing at an external database — as distinct from sibling formats [[open-document-text]], [[open-document-spreadsheet]], [[open-document-presentation]].
Open Document Formula — Use when asked about OpenDocument Formula (`.odf`) files — the ISO/IEC 26300 ZIP+XML mathematical-equation format built on MathML, or its conversion to/from Word's equation editor — as distinct from "ODF" the umbrella acronym for the whole OpenDocument Format family, and from sibling formats [[open-document-text]], [[open-document-spreadsheet]], [[open-document-presentation]].
Open Document Graphics — Use when asked about OpenDocument Graphics (`.odg`) files — the ISO/IEC 26300 ZIP+XML vector-drawing format, its multi-page/multi-layer document model, or how it differs from a single-image format like SVG — as distinct from sibling formats [[open-document-text]], [[open-document-spreadsheet]], [[open-document-presentation]].
Open Document Presentation — Use when asked about OpenDocument Presentation (`.odp`) files — the ISO/IEC 26300 ZIP+XML slide-deck format, its package structure, or conversion to/from `.pptx` — as distinct from [[microsoft-powerpoint]]'s proprietary format, [[google-slides]] (a tool that can import/export ODP, not the format itself), and sibling formats [[open-document-text]], [[open-document-spreadsheet]], [[open-document-graphics]].
Open Document Spreadsheet — Use when asked about OpenDocument Spreadsheet (`.ods`) files — the ISO/IEC 26300 ZIP+XML spreadsheet format, its OpenFormula formula syntax, or conversion to/from `.xlsx` — as distinct from [[microsoft-excel]]'s proprietary format, [[google-sheets]] (a tool that can import/export ODS, not the format itself), and sibling formats [[open-document-text]], [[open-document-presentation]], [[open-document-graphics]].
Open Document Text — Use when asked about OpenDocument Text (`.odt`) files — the ISO/IEC 26300 ZIP+XML word-processing format, its package structure, or conversion to/from `.docx` — as distinct from [[microsoft-word]]'s proprietary format, [[google-docs]] (a tool that can import/export ODT, not the format itself), and sibling formats [[open-document-spreadsheet]], [[open-document-presentation]], [[open-document-graphics]].

Public sector & sustainability 9

Environmental Impact Assessment — Use when asked to plan, write, or review an environmental impact assessment — a systematic evaluation of the likely environmental effects of a proposed project or policy before it proceeds, often required by law for larger projects — distinct from a [[sustainability-report]], which discloses an organization's ongoing performance rather than a single project's predicted impact.
Freedom of Information Request — Use when asked to draft or advise on a freedom of information request — a formal request to a government body for access to official records or information under public-records law (e.g. FOIA in the US, the FOI Act in the UK) — noting that the specific law, process, and exemptions vary by country and even by agency.
Government Bill Drafting — Use when asked to draft proposed legislation — a bill, act, or ordinance intended for formal introduction to a legislative body — noting that the format, drafting conventions, and terminology vary by legislative body and level of government (a bill introduced in the US Congress, a UK Parliament bill, a state or provincial legislature's bill, and a local council ordinance each follow their own house rules and drafting style).
Government Legislative Testimony — Use when asked to prepare or write legislative testimony — a witness's prepared statement delivered to a legislative committee to inform a pending bill or inquiry — noting that hearing format, submission rules, and terminology vary by legislative body and level of government (a US Congressional committee hearing, a UK Parliamentary select committee session, and a state or provincial legislature's committee hearing each follow their own procedures).
Government Public Comment Response — Use when asked to draft a government agency's formal response to public comments received on a proposed rule or policy during a notice-and-comment or public consultation period — noting that the process, legal requirements, and terminology vary by country and level of government (the US federal rulemaking process's comment period and "response to comments" document differ from an equivalent public consultation response elsewhere, or from a state, provincial, or local process).
Government Public Consultation — Use when asked to design or run a public consultation — a structured, proactive process for gathering public input before a government decision is made — noting that the legal requirements, formats, and terminology vary by country and level of government (a UK government consultation, a US federal or state public-input process, and a local council consultation each follow their own rules for scope, notice, and duration).
Government Regulatory Impact Assessment — Use when asked to write or review a regulatory impact assessment (RIA) — an analysis of the likely costs, benefits, and effects of a proposed regulation before it is adopted, often legally required for significant rules — noting that the specific requirement, methodology, and review body vary by country and level of government (a US federal agency's analysis under executive-order review differs from a UK or EU regulatory impact assessment, a state or provincial requirement, or a local rule with no formal requirement at all).
Policy Brief — Use when asked to write a policy brief — a concise, decision-oriented document that summarizes a policy issue and recommends a course of action to a specific decision-maker — distinct from a full research report, which exists to lay out the evidence base rather than drive an immediate decision.
Sustainability Report — Use when asked to write, review, or structure a sustainability report — a disclosure of an organization's environmental, social, and governance (ESG) performance, often against a recognized framework or standard — distinct from an [[environmental-impact-assessment]], which evaluates a single project's predicted impact before it proceeds rather than an organization's ongoing performance.

Public value 2

Public Value Guide — Use when the user asks about public value, public administration, public policy, government management, or social-sector and nonprofit management, wants to run a team workshop on one of these topics, or wants to assess their organization's maturity against a public-value practice. Routes to the right topic of the Public Value Guide and answers from the book's own text. Trigger phrases include "public value," "strategic triangle," "government failure," "public administration," "social sector," and "nonprofit management." Companion to [[public-value-metrics]], which covers measuring and justifying public value; for health spending see [[health-economics-guide]].
Public Value Metrics — Use when the user asks to explain a public-value concept, compute a metric such as social return on investment, value for money, or cost per outcome, apply Green Book appraisal, or build a business case for government or social-sector software, using the Public Value Metrics book as the grounded source of formulas, worked examples, and pitfalls. Companion to [[public-value-guide]], which covers practice rather than measurement; for health-specific economics see [[health-economics-metrics]].

Research & analysis methods 10

Cognitive Task Analysis — Use when asked to uncover the mental processes and decision-making behind a task — interviews, think-aloud protocol, knowledge elicitation, cognitive workload assessment — as the mental-process-focused counterpart to task-analysis's more general, observable-steps focus.
Critical Incident Technique — Use when asked to gather and analyze detailed accounts of significant events — define/collect/select/code/cluster/interpret — as a qualitative research method focused on specific incidents rather than routine task execution (see task-analysis).
Diary Study — Use when asked to run a diary study — recruitment, guidelines, diary keeping, data collection, analysis, reporting — a longitudinal qualitative research method for capturing experiences, behaviors, and thoughts as they unfold over time, from participants' own ongoing records.
Hierarchical Task Analysis — Use when asked to decompose a complex task into a hierarchical structure of subtasks, actions, and operations — task identification, decomposition, relationships, documentation, evaluation — as the structural-decomposition specialization of task-analysis.
Literature Review — Use when asked to write or conduct a literature review — a systematic survey and synthesis of existing published work on a topic, done before or alongside new research — as distinct from a [[research-proposal]], which proposes new work and often uses the review's findings to justify why that new research is needed.
Research Proposal — Use when asked to write a research proposal — a document laying out a specific research question, method, and plan, usually to secure approval or ethics sign-off — as distinct from a [[grant-proposal]], which specifically requests funding and is often built around one; a research proposal can exist with no funding ask at all.
Survey Design — Use when asked to design a survey, questionnaire, or feedback form — writing questions and response scales that actually measure what they're meant to without leading or confusing respondents — as distinct from a [[user-interview-guide]], which is a qualitative, open-ended conversation rather than a standardized instrument.
Task Analysis — Use when asked to break down a complex task or activity into its component steps — the identify/collect/decompose/sequence/document/evaluate/improve process — as the general umbrella technique behind more specific methods like hierarchical-task-analysis and cognitive-task-analysis.
User Interview Guide — Use when asked to prepare questions for a user interview, customer interview, or discovery call — a qualitative conversation structured to surface real behavior and needs — as distinct from [[survey-design]], which is a standardized written instrument rather than an adaptive spoken conversation.
Workflow Analysis — Use when asked to examine how work actually flows through a process or organization — workflow mapping, time analysis, data-flow analysis, roles/responsibilities, decisions, controls — as the process-level counterpart to task-analysis's single-task focus.

Sales & customer success 6

Churn Analysis — Use when asked to analyze customer churn — why and when customers stop using a product or service — to separate preventable churn from unavoidable churn, and to turn a raw churn rate into something actionable.
Customer Onboarding — Use when asked to design or write a customer onboarding plan — the process of getting a new customer from purchase to first real value — distinct from [[employee-onboarding]], which ramps a new hire rather than a new customer.
Customer Success Plan — Use when asked to write or maintain a customer success plan — an ongoing plan for a specific customer's outcomes after onboarding — distinct from [[customer-onboarding]], which covers only the initial ramp to first value.
Net Promoter Score — Use when asked to set up, calculate, or interpret Net Promoter Score (NPS) — a customer-loyalty metric from a single 0-10 "how likely to recommend" survey question sorting respondents into promoters, passives, and detractors.
Sales Pitch — Use when asked to write or refine a sales pitch — a concise spoken or written narrative persuading a specific audience to buy, invest, or adopt — distinct from a full [[sales-proposal]], which is the detailed written follow-through once the pitch has landed.
Sales Proposal — Use when asked to write or review a sales proposal — a formal document proposing a specific solution, scope, and price to a prospective buyer, often in response to a buyer's [[request-for-proposal]] — distinct from a [[statement-of-work]], which governs execution once the deal is won.

Software Engineering › Databases 6

MariaDB Database — Use when asked to write or debug MariaDB-specific SQL, choose a storage engine, or explain where MariaDB diverges from MySQL (syntax it added, features it dropped, replication/compatibility gaps) — independent of any specific ORM or client library. For syntax and behavior MariaDB shares with MySQL, see mysql-database.
MSSQL Database — Use when asked to write or debug T-SQL for Microsoft SQL Server, choose an index or isolation level, configure or tune a SQL Server instance, or explain SQL Server-specific features (T-SQL extensions, the query optimizer, Always On/replication) — independent of any specific driver or ORM.
MySQL Database — Use when asked to write or debug MySQL-specific SQL, choose a storage engine or index type, configure or tune a MySQL/MariaDB instance, or explain MySQL-specific behavior (InnoDB locking, replication, the SQL-mode/strict-mode differences from standard SQL) — independent of any specific ORM or client library.
Oracle Database — Use when asked to write or debug PL/SQL or Oracle-specific SQL, choose an index or partitioning strategy, configure or tune an Oracle Database instance, or explain Oracle-specific features (sequences, PL/SQL packages, MVCC via undo, RAC) — independent of any specific driver or ORM.
PostgreSQL Database — Use when asked to write or debug PostgreSQL-specific SQL, choose a data type or index type, configure or tune a Postgres instance, or explain PostgreSQL-specific features (JSONB, CTEs, window functions, extensions, MVCC/vacuum) — independent of any specific ORM or client library.
SQLite Database — Use when asked to write or debug SQLite-specific SQL, understand its dynamic/manifest typing, configure WAL mode or concurrency behavior, or decide whether SQLite fits a given use case — independent of any specific driver or ORM.

Software Engineering › Web formats 8

CSS — Use when asked to write, explain, or debug CSS — selectors and specificity, the box model, Flexbox/Grid layout, responsive design with media queries, or why a style isn't applying — independent of any specific framework or CSS-in-JS tool.
HTML — Use when asked to write, explain, or debug plain HTML — document structure, semantic elements, forms, accessibility attributes, or how the browser parses and renders markup — independent of any specific framework or templating language.
JSON — Use when asked to write, validate, or debug JSON — syntax rules, JSON Schema validation, JSON Lines (NDJSON), or common serialization pitfalls (numbers, duplicate keys, trailing commas) — independent of any specific language's JSON library.
Markdown — Use when asked to write or fix Markdown formatting — headings, lists, links, tables, code fences, front matter — or to explain differences between CommonMark and GitHub Flavored Markdown (GFM).
SQL — Use when asked to write or debug standard/portable SQL — joins, aggregation, subqueries vs CTEs, transactions, normalization — independent of any specific database vendor. For a vendor's own dialect and tuning specifics, use its own skill (postgresql-database, mysql-database, mssql-database, oracle-database, sqlite-database).
TOML — Use when asked to write, validate, or debug TOML — tables, arrays of tables, inline tables, and TOML's stricter typing versus YAML/JSON — independent of any specific tool's config schema (Cargo.toml, pyproject.toml, etc.).
XML — Use when asked to write, parse, or validate XML — element/attribute syntax, namespaces, XPath queries, or schema validation with XSD/DTD — independent of any specific XML-based format (SVG, RSS, config files) built on top of it.
YAML — Use when asked to write, validate, or debug YAML — indentation-based syntax, anchors/aliases, multi-document files, or common parsing pitfalls (the Norway problem, tabs, string quoting) — independent of any specific tool's YAML dialect (CI config, Kubernetes manifests, etc.).

Software Engineering › Programming Languages 19

C++ Programming — Use when asked to write, explain, or debug general-purpose C++ code — RAII and smart pointers, classes and templates, move semantics — as the object-oriented/generic-programming superset built on c-programming.
C Programming — Use when asked to write, explain, or debug general-purpose C code — pointers and manual memory management, structs, the preprocessor, undefined behavior — as the low-level foundation c-plus-plus-programming builds on.
C# Programming — Use when asked to write, explain, or debug general-purpose C# code — properties and classes, LINQ, async/await, nullable reference types — independent of the broader dot-net-programming platform/runtime or any specific .NET framework (ASP.NET Core, Blazor).
Delphi Programming — Use when asked to write, explain, or debug Delphi/Object Pascal code — classes and interfaces, properties, the VCL/FireMonkey component model, units — as the object-oriented dialect built on pascal-programming.
.NET Programming — Use when asked about the .NET platform/runtime and tooling itself — the CLR, the base class library, project SDKs and NuGet, cross-language interop — as distinct from any one .NET language (see c-sharp-programming) or framework (see blazor-programming).
Go Programming — Use when asked to write, explain, or debug general-purpose Go code — goroutines and channels, error handling idioms, interfaces, modules — independent of any specific framework.
JavaScript Programming — Use when asked to write, explain, or debug general-purpose JavaScript code — language fundamentals (scoping, closures, `this`, prototypes/classes), async code with Promises/async-await, modules (ESM vs CommonJS), or common runtime pitfalls — independent of any testing framework or UI library.
Julia Programming — Use when asked to write, explain, or debug general-purpose Julia code — multiple dispatch, type stability for performance, broadcasting, the package manager — for high-performance numerical/scientific computing, distinct from r-programming's statistics-first focus.
Kotlin Programming — Use when asked to write, explain, or debug general-purpose Kotlin code — null safety, data classes, coroutines, extension functions — independent of any specific target (Android, JVM backend, Kotlin Multiplatform).
Lisp Programming — Use when asked to write, explain, or debug general-purpose Lisp code (Common Lisp) — s-expressions, macros/code-as-data, recursion — as the historical family scheme-programming is a smaller, more minimalist dialect within.
Objective-C Programming — Use when asked to write, explain, or debug general-purpose Objective-C code — message-passing syntax, properties and ARC, protocols, interop with C — as the predecessor language swift-programming largely supersedes on Apple platforms.
Pascal Programming — Use when asked to write, explain, or debug general-purpose (standard/Free) Pascal code — strong static typing, structured programming constructs, units — as the language delphi-programming's Object Pascal dialect extends.
Python Programming — Use when asked to write, explain, or debug general-purpose Python code — language idioms (comprehensions, generators, context managers), typing, virtual environments/packaging, or common runtime pitfalls (mutable default arguments, the GIL) — independent of any testing framework or web framework.
R Programming — Use when asked to write, explain, or debug general-purpose R code — vectors and vectorization, data frames, the tidyverse/base-R split, functions — for statistical computing and data analysis, distinct from julia-programming's numerical-computing focus.
Rust Programming — Use when asked to write, explain, or debug general-purpose Rust code — ownership and borrowing, `Result`/`Option` error handling, traits and generics, or Cargo workflows — independent of any testing framework or web/UI crate.
Scheme Programming — Use when asked to write, explain, or debug general-purpose Scheme code — minimal core syntax, tail-call optimization, first-class continuations — as the smaller, more minimalist Lisp dialect distinct from lisp-programming (Common Lisp).
Swift Programming — Use when asked to write, explain, or debug general-purpose Swift code — optionals, structs vs classes, protocols and protocol-oriented programming, async/await — independent of any UI framework (SwiftUI, UIKit).
TypeScript Programming — Use when asked to write, explain, or debug general-purpose TypeScript code — the type system (interfaces, generics, unions, narrowing), tsconfig options, or common typing pitfalls (`any` vs `unknown`, structural typing) — independent of any testing framework or UI library.
Zig Programming — Use when asked to write, explain, or debug general-purpose Zig code — explicit error handling and no hidden control flow, comptime, manual memory management with allocators — as a modern, safer alternative in the same low-level niche as c-programming.

Software Engineering › Web frameworks 7

Angular Programming — Use when asked to write, explain, or debug general-purpose Angular code — components and templates, dependency injection, signals/RxJS-based reactivity, modules/standalone components — as a TypeScript UI framework, distinct from lily-design-system-angular's specific component package built on it.
Blazor Programming — Use when asked to write, explain, or debug general-purpose Blazor code — components/razor syntax, Server vs. WebAssembly hosting models, data binding, dependency injection — as a C#/.NET UI framework, distinct from lily-design-system-blazor's specific component package built on it.
Nunjucks Programming — Use when asked to write, explain, or debug general-purpose Nunjucks templates — variables/filters, template inheritance, control structures, autoescaping — as a JavaScript server-side templating engine, distinct from lily-design-system-nunjucks's specific template/macro package built on it.
React Programming — Use when asked to write, explain, or debug general-purpose React code — components and JSX, hooks (useState/useEffect), the virtual DOM/reconciliation — as a JavaScript/TypeScript UI library, distinct from lily-design-system-react's specific component package built on it.
Svelte Programming — Use when asked to write, explain, or debug general-purpose Svelte code — compile-time reactivity, runes ($state/$derived/$effect), single-file components, SvelteKit basics — as a JavaScript/TypeScript UI framework, distinct from lily-design-system-svelte's specific component package built on it.
Sveltia I18n — Use when adding internationalization to a Svelte or SvelteKit app with the sveltia-i18n library (`@sveltia/i18n`) — a Svelte 5 runes-based i18n library that uses Unicode MessageFormat 2 (MF2) for message syntax instead of ICU MessageFormat 1 or ad hoc placeholder formats. Distinct from [[svelte-programming]] (the framework itself) and [[unicode-messageformat]] (the message syntax it relies on).
Vue Programming — Use when asked to write, explain, or debug general-purpose Vue code — the Composition API, reactivity (ref/reactive), single-file components, directives — as a JavaScript/TypeScript UI framework, distinct from lily-design-system-vue's specific component package built on it.

Software Engineering › Playwright testing 4

Playwright Testing With JavaScript — Use when asked to write, explain, debug, or extend Playwright browser automation code in JavaScript — locating elements, performing actions, waiting, and writing real assertions with @playwright/test.
Playwright Testing With Python — Use when asked to write, explain, debug, or extend Playwright browser automation code in Python — locating elements, performing actions, waiting, and writing real assertions with pytest-playwright.
Playwright Testing With Rust — Use when asked to write, explain, debug, or extend Playwright browser automation code in Rust using the playwright-rs crate — locating elements, performing actions, waiting, and writing real assertions.
Playwright Testing With TypeScript — Use when asked to write, explain, debug, or extend Playwright browser automation code in TypeScript — locating elements, performing actions, waiting, and writing real assertions with @playwright/test.

Software Engineering › Selenium testing 4

Selenium Testing With JavaScript — Use when asked to write, explain, debug, or extend Selenium WebDriver browser automation code in JavaScript — locating elements, performing actions, explicit waits, and writing real assertions with Mocha.
Selenium Testing With Python — Use when asked to write, explain, debug, or extend Selenium WebDriver browser automation code in Python — locating elements, performing actions, explicit waits, and writing real assertions with pytest.
Selenium Testing With Rust — Use when asked to write, explain, debug, or extend Selenium-style WebDriver browser automation code in Rust using the thirtyfour crate — locating elements, performing actions, explicit waits, and writing real assertions.
Selenium Testing With TypeScript — Use when asked to write, explain, debug, or extend Selenium WebDriver browser automation code in TypeScript — locating elements, performing actions, explicit waits, and writing real assertions with Mocha.

Software Engineering › Editors 3

Emacs — Use when asked to write or debug Emacs Lisp, configure Emacs (init.el/early-init.el, use-package, package.el/straight.el), explain Emacs keybinding notation, or work with buffers, windows, frames, and major/minor modes.
Vim — Use when asked to write Vim/Neovim keybindings or config (.vimrc, init.vim, init.lua), explain Vim's modal editing model or motion/operator grammar, write Vimscript or Neovim Lua config, or debug plugin setups (vim-plug, packer.nvim, lazy.nvim).
Vix — Use when asked about Vix IDE — what it is, how to install/run/configure it, its keyboard-driven features (editor, file explorer, Git, DB workbench, LSP, Org mode, debugger), or how to work on its own codebase (Cargo workspace, `vix-*` member crates, spec-driven development, hard build rules).

Software Engineering › Org mode 3

Org Contacts — Use when asked to manage contacts in Emacs using org-contacts — storing people as Org headlines with properties, searching/completing by name or email, and integrating with message composition — as an Org mode extension (see org-mode), distinct from org-roam's networked-notes model (see org-roam).
Org Mode — Use when asked to write or edit Org mode files (.org) — headline/outline syntax, TODO workflows, tables, links, properties, the agenda, or Babel code blocks — whether inside Emacs or as a plain-text format read by other tools.
Org Roam — Use when asked to build a networked "second brain" of notes in Emacs using org-roam — bidirectional linking, the node/backlink model, and the daily-notes workflow — as an Org mode extension (see org-mode), distinct from org-contacts' single-purpose contact list (see org-contacts).

Statistics 7

Anomaly Analysis — Use when asked to detect anomalies/outliers in data — statistical, machine-learning, and deep-learning detection methods, supervised vs. unsupervised approaches — as distinct from trend-analysis's focus on overall patterns over time rather than individual deviant points.
Bayes Theorem Analysis — Use when asked to apply Bayes' theorem — updating a probability estimate given new evidence, P(A|B) = P(B|A)·P(A)/P(B) — as one specific probabilistic technique within the broader statistical-analysis toolkit (see statistical-analysis), foundational to Bayesian inference and Bayesian networks.
Chi Square Analysis — Use when asked to test whether two categorical variables are significantly associated — contingency tables, observed vs. expected frequencies, the chi-square test statistic — as one specific inferential-statistics technique within the broader toolkit (see statistical-analysis).
Constraint Satisfaction — Use when asked to model or solve a constraint satisfaction problem (CSP) — variables, domains, and constraints solved via backtracking, forward checking, or constraint propagation — as distinct from Monte Carlo methods (see monte-carlo-analysis), which use random sampling rather than systematic constraint solving.
Monte Carlo Analysis — Use when asked to solve a mathematical or engineering problem via repeated random sampling — the general Monte Carlo computational method — as distinct from monte-carlo-testing's specific application of the same underlying technique to software reliability testing.
Statistical Analysis — Use when asked which statistical technique fits a data question — descriptive vs. inferential statistics, regression, time series, factor/cluster analysis, data mining — as the umbrella technique-selection layer above more specific methods like bayes-theorem-analysis, chi-square-analysis, and monte-carlo-analysis.
Trend Analysis — Use when asked to analyze data over time to identify patterns and forecast — regression, moving averages, exponential smoothing — as distinct from anomaly-analysis's focus on individual deviant points rather than the overall directional pattern.

Strategic effects 9

Strategic Flywheel Effects — Use when asked about the flywheel effect — small, continuous efforts compounding into significant momentum over time — as a strategic-growth model distinct from strategic-network-effects (which depends on user count specifically) and strategic-viral-effects (which depends on sharing specifically).
Strategic Leverage Effects — Use when asked about (operating) leverage effects — how fixed costs amplify the impact of sales changes on profitability, in either direction — as a financial-structure effect distinct from the growth-oriented strategic effects (network, platform, scale) elsewhere in this collection.
Strategic Moat Effects — Use when asked about a competitive "moat" — a durable competitive advantage (brand, technology, user base, exclusive resources) that defends market position — as the umbrella concept several other strategic effects (strategic-network-effects, strategic-platform-effects, strategic-scale-effects) are specific sources of.
Strategic Monopoly Effects — Use when asked about monopoly effects — the economic and social consequences of a market dominated by a single company (reduced innovation, pricing power, barriers to entry) — as the extreme, socially concerning endpoint several other strategic effects (network, platform, scale, moat) can lead toward.
Strategic Network Effects — Use when asked about network effects — a product or service becoming more valuable as more people use it (Metcalfe's Law), direct vs. indirect network effects — as one of several related strategic effects (see also strategic-platform-effects, strategic-viral-effects) that can create durable competitive advantage.
Strategic Platform Effects — Use when asked about the platform effect — a platform's value increasing as more users AND third-party developers join and build on it — as a broader driver of, and complement to, strategic-network-effects specifically on multi-sided platforms.
Strategic Scale Effects — Use when asked about scale effects — how a business's size affects its costs, revenues, and profitability through economies of scale, network effects, and learning effects — as an umbrella concept combining several distinct mechanisms.
Strategic Threshold Effects — Use when asked about threshold effects — a tipping point where crossing a critical level causes significant, often non-linear change (economies of scale, market penetration, technology adoption) — as a pattern underlying several other strategic effects in this collection.
Strategic Viral Effects — Use when asked about viral effects — a product or service spreading rapidly through word-of-mouth or social sharing — as a growth mechanism distinct from strategic-network-effects (value from usage) and strategic-flywheel-effects (compounding operational effort).

Supply chain & operations 5

Capacity Planning — Use when asked to determine whether available capacity — production, staffing, or infrastructure — will meet projected demand, and what to do about a gap or a surplus in either direction, as distinct from [[demand-forecasting]], which produces the demand projection capacity planning is measured against rather than deciding what to do about it.
Demand Forecasting — Use when asked to project future customer demand for operational planning — how much to produce, stock, or staff for — as distinct from [[demand-analysis]] (market-sizing and opportunity assessment for a business decision) which this is not; demand forecasting is the ongoing operational forecast that drives inventory and capacity decisions.
Inventory Management — Use when asked to set up or improve inventory control — reorder points, safety stock, ABC classification, cycle counts — as distinct from [[demand-forecasting]] (the demand projection that feeds inventory decisions) and [[logistics-planning]] (how goods physically move once they're in the supply chain).
Logistics Planning — Use when asked to plan how goods physically move from origin to destination — transportation mode, routing, timing, handoffs — as distinct from the broader [[supply-chain-risk-assessment]], which identifies what could go wrong across the whole chain rather than laying out the concrete plan for moving goods.
Supply Chain Risk Assessment — Use when asked to identify and prioritize risks across a supply chain — supplier concentration, geographic or geopolitical exposure, single points of failure — as distinct from [[logistics-planning]], which is the concrete operational plan for moving goods rather than the exercise of finding what could go wrong along the way.

Teaching › Classroom practice 16

Classroom Management — Use when asked to set up the routines, procedures, and behavior systems that keep a whole class running — as distinct from [[student-behavior-intervention-plan]], which targets one student's specific behavior pattern rather than the group's shared systems.
Classroom Seating Chart — Use when asked to arrange where students sit for behavior management, learning needs, and social dynamics — as distinct from [[classroom-management]], the broader system of routines and procedures this seating layout is one specific tool within.
Classroom Technology Integration — Use when deciding whether and how a digital tool genuinely serves a lesson's learning objective rather than being used for its own sake, as distinct from [[instructional-materials-selection]], the broader process of selecting all course materials that digital tools are one category within.
Cooperative Learning Structures — Use when designing structured small-group or peer activities — think-pair-share, jigsaw, numbered heads together — with individual accountability built in, as distinct from [[differentiated-instruction]], the broader adaptation strategy this is one instructional method within.
Differentiated Instruction — Use when asked to adapt content, process, product, or environment to varied learner readiness, interest, or profile within a lesson — as distinct from [[individualized-education-program]], a formal legal document written for one student with a disability rather than an informal adjustment available to any learner.
English Language Learner Support — Use when planning how a student who is still acquiring the language of instruction will access grade-level content — language objectives, scaffolds, and comprehensible input — as distinct from [[differentiated-instruction]], which adapts to readiness rather than to language proficiency.
Exit Ticket — Use when asked to design a short end-of-lesson prompt or task that checks whether today's objective landed — as distinct from [[formative-assessment]], the broader practice of checking understanding throughout a lesson, of which this is one specific technique.
Formative Assessment — Use when asked to design ongoing, in-the-moment checks for understanding during instruction — as distinct from [[summative-assessment]], which evaluates mastery after a unit or course is finished rather than while it's still being taught.
Gifted and Talented Enrichment — Use when planning extension work for a student who has already mastered grade-level content and needs depth or complexity beyond it, as distinct from [[differentiated-instruction]], which adapts across the full readiness range rather than only for advanced learners.
Individualized Education Program — Use when asked to draft or plan an IEP for a student with a disability under special education law — goals, services, and accommodations — as distinct from a [[student-behavior-intervention-plan]], which addresses only a behavior pattern, and from general [[differentiated-instruction]], which is informal and applies to any learner rather than being a legally binding document for one specific student.
Lesson Plan — Use when asked to plan a single teaching session — objective, hook, main activity, check for understanding, and materials — as distinct from [[curriculum-design]], which plans the overall course or program a lesson plan belongs to.
Parent Teacher Conference — Use when planning and running a live meeting with a student's parent or guardian about academic or behavioral progress, as distinct from [[report-card-comments]], the written, asynchronous counterpart to this conversation.
Report Card Comments — Use when writing individualized narrative comments that summarize a student's progress for a report card under tight per-student time and space limits, as distinct from [[parent-teacher-conference]], the live, two-way conversation this written summary is the counterpart to.
Restorative Classroom Circle — Use when running a structured circle to address conflict or harm, or to build classroom community, through shared dialogue rather than punitive discipline, as distinct from [[classroom-management]], the broader preventive day-to-day system this is one response within.
Student Behavior Intervention Plan — Use when asked to build a targeted plan addressing one student's specific, recurring behavior pattern — functional assessment, replacement behaviors, data tracking — as distinct from [[classroom-management]], which sets up whole-group systems, and [[individualized-education-program]], the broader legal document a behavior plan may sit inside.
Substitute Lesson Plan — Use when asked to prepare a lesson or day plan for a substitute teacher who doesn't know the class, its routines, or its students — as distinct from an ordinary [[lesson-plan]], which is written for the regular teacher who already knows all of that.

Teaching › Curriculum development 11

Competency Based Education Design — Use when asked to design a curriculum structured around demonstrated mastery of defined competencies rather than seat time or fixed pacing, as distinct from [[curriculum-design]], whose general sequence-and-pacing model assumes a fixed calendar that this is a specific alternative structural approach to.
Course Syllabus Design — Use when asked to write the student- or parent-facing document describing a course — policies, grading scheme, unit schedule, expectations — as distinct from [[curriculum-design]], the internal instructional planning this document communicates outward rather than substitutes for.
Curriculum Design — Use when asked to design the overall sequence and structure of a course or training program — outcomes, unit sequence, assessment points, pacing — made up of individual [[lesson-plan]]s, as distinct from planning a single session.
Curriculum Mapping — Use when asked to audit curriculum across multiple courses or grade levels for standards coverage, gaps, redundancy, and vertical alignment, as distinct from [[curriculum-design]], which designs one course, and [[learning-standards-alignment]], which maps one curriculum to a standards document rather than comparing across curricula.
Instructional Materials Selection — Use when asked to evaluate and choose textbooks, resources, or materials for a course or curriculum against learning objectives, cost, and accessibility, as distinct from [[classroom-technology-integration]], which is focused specifically on digital tools — one category within this broader selection process.
Learning Standards Alignment — Use when asked to map lessons, units, or a curriculum to external learning standards (state standards, Common Core, NGSS) and document where each one is addressed, as distinct from [[curriculum-mapping]], which audits alignment and coverage gaps across multiple courses or grade levels rather than against a single external standards document.
Program Evaluation — Use when asked to evaluate, after implementation, whether a curriculum or educational program actually achieved its intended outcomes, as distinct from [[curriculum-design]], which designs the program beforehand, and [[training-needs-analysis]], which identifies a gap before any program exists.
Rubric Design — Use when asked to build a scoring rubric — criteria and performance-level descriptors for grading student work consistently — as distinct from [[formative-assessment]] and [[summative-assessment]], which decide when and what to assess; a rubric is the scoring instrument used once that decision is already made.
Summative Assessment — Use when asked to design an end-of-unit or end-of-course assessment (test, final project, exam) that evaluates whether mastery was reached, as distinct from [[formative-assessment]], which is an ongoing, low-stakes check during instruction meant to inform teaching rather than assign a grade.
Training Needs Analysis — Use when asked to identify the actual gap between current and needed skills or knowledge before building training — root cause, target audience, success measure — so training solves a real, specific gap rather than being commissioned on a generic assumption; distinct from [[curriculum-design]], which designs the program once a genuine training need is confirmed.
Unit Plan — Use when planning a sequence of related lessons that share a unit-level objective and build to a unit assessment — the layer between a single [[lesson-plan]] and the whole-course [[curriculum-design]] it belongs to.

Team practices 3

Forming Storming Norming Performing — Use when asked to explain or apply Tuckman's stages of group development — Forming, Storming, Norming, Performing — as a non-linear model for understanding where a team currently stands, not a fixed sequence every team must complete once.
Icebreaker Questions — Use when asked to write or choose icebreaker questions for a new or newly-formed group — personal, funny, hypothetical, and reflective question types — to build comfort and camaraderie, with attention to group size and inclusivity.
TEAM FOCUS — Use when asked to apply McKinsey's TEAM FOCUS framework — the interpersonal TEAM half (Talk, Evaluate, Assist, Motivate) and the analytical FOCUS half (Frame, Organize, Collect, Understand, Synthesize) — for structuring both team dynamics and a problem-solving process together.

Technology › AI 7

Claude AI — Use when asked what Claude is, which Claude model/tier to pick, or how Claude (Anthropic's assistant) differs from other AI assistants at a product level. For API mechanics — model ids, pricing, streaming, tool use, MCP, prompt caching, token counting, model migration — use the `claude-api` skill instead; it stays current, this one doesn't repeat that detail.
GB1 AI — Use when asked what GB1 is — a UK-based privacy-focused AI assistant from Locai Labs. Verify current pricing/availability at gb1.ai before repeating specifics from this file; it's a small, actively-changing product and the facts here were captured from the site on 2026-09-05.
Gemini AI — Use when asked what Google's Gemini is, how to call the Gemini API (Google AI Studio / Vertex AI), its multimodal and function-calling capabilities, or how it compares to other model providers. Verify current model names/pricing against Google's docs — this file covers stable shape, not a specific model generation's numbers.
Glimmer AI — Use when asked what Meta's Muse Glimmer is — an open-source, on-device agentic model from Meta for always-on local agents. Verify current specifics at developer.meta.com/ai/lp/muse-glimmer before repeating details from this file; it's a fast-moving open model release and the facts here were captured on 2026-09-05.
GPT AI — Use when asked what OpenAI's GPT/ChatGPT is, how to call the OpenAI API (Chat Completions vs the Responses API), its function-calling and structured-output features, or how it compares to other model providers. Verify current model names/pricing against OpenAI's docs — this file covers stable shape, not a specific model generation's numbers.
Mistral AI — Use when asked what Mistral AI is, how to call its API (La Plateforme), its open-weight vs proprietary model lines, or how it compares to other model providers. Verify current model names/pricing against Mistral's docs — this file covers stable shape, not a specific model generation's numbers.
Ollama AI — Use when asked to install, run, or script against Ollama — pulling and running local open-weight LLMs, writing a Modelfile, or calling its local REST/OpenAI-compatible API from code.

Technology › Data & ML 6

Data Governance — Use when asked to define or document data governance — the policies, ownership, and processes for how an organization manages its data as an asset (who owns a dataset, how it's classified, how long it's retained, who can request access) — as distinct from [[data-quality]], which is the measurable property those policies aim to protect, not the framework itself.
Data Pipeline — Use when asked to design, document, or troubleshoot a data pipeline — an automated sequence that extracts data from a source, transforms it, and loads it into a destination on a schedule or trigger — as distinct from [[data-quality]], which measures whether the data moving through the pipeline is actually accurate and complete, not how it's moved.
Data Quality — Use when asked to define, measure, or improve data quality — whether data is accurate, complete, consistent, and fit for its actual use — as distinct from [[data-governance]], which is the policy and ownership framework around data, not the measurable property of the data itself.
Machine Learning Model Card — Use when asked to write or review a model card — a document accompanying a trained ML model that describes what it does, how it was trained and evaluated, and its known limitations — as distinct from [[mlops]], which covers the infrastructure for deploying and monitoring a model rather than documenting it for downstream users.
MLOps — Use when asked about MLOps — the practices and infrastructure for deploying, monitoring, and maintaining ML models in production reliably — as distinct from the model-development and training work itself, and from [[machine-learning-model-card]], which documents a model for downstream users rather than operating it once it's live.
Prompt Engineering — Use when asked to write, improve, or debug a prompt for a language model — getting reliable, intended behavior through specific instructions, examples, and context — as distinct from [[machine-learning-model-card]], which documents a trained model's capabilities and limits rather than shaping its behavior through the prompt.

Technology › Software engineering 19

Arc42 — Use when asked to document a software architecture using the arc42 template — its twelve sections (context, solution strategy, building blocks, runtime/deployment views, cross-cutting concepts, decisions, quality requirements, risks) — as a documentation structure that pairs with diagram types like component-diagram and deployment-diagram rather than replacing them.
Back End Design — Use when asked to design the server-side layer of a software system — API design, data persistence, business logic, scalability, security — as the server-facing counterpart to front-end-design.
Domain Driven Design — Use when asked to apply Domain-Driven Design (DDD) — ubiquitous language, bounded contexts, entities/value objects, aggregates, domain events — as a software-design approach for aligning code structure with business domain concepts, complementing class-diagram's structural notation and package-diagram's module organization.
Evolutionary Architecture — Use when asked to design a software architecture that supports incremental, guided change over time — architectural fitness functions, incremental change, appropriate coupling across multiple architectural dimensions — as distinct from a one-time upfront design, and the architectural counterpart to evolutionary-engineering's practice-level focus.
Evolutionary Engineering — Use when asked to set up engineering practices that support continuous, incremental software change — continuous integration/delivery, automated testing, trunk-based development, feature flags, refactoring — as the practice-level counterpart to evolutionary-architecture's structural focus.
Front End Design — Use when asked to design the client-side/UI layer of a software system — component structure, layout and responsiveness, state management, accessibility, performance — as the client-facing counterpart to back-end-design, and distinct from visual/UX design (see user-centred-design).
Low Code — Use when asked about low-code development platforms — visual/drag-and-drop workflows with some custom scripting, target use cases, trade-offs vs. traditional development — as the more customizable sibling of no-code.
Model View Controller — Use when asked to explain or apply the Model-View-Controller (MVC) architectural pattern — separating data/business logic (Model), presentation (View), and coordinating logic (Controller) — as one specific software-architecture pattern among others.
No Code — Use when asked about no-code development platforms — fully visual configuration with zero hand-written code, target use cases, trade-offs and limits — as the more restrictive sibling of low-code.
Refactoring — Use when asked to improve existing code's internal structure without changing its external behavior — rename, extract, replace conditionals with polymorphism, and other restructuring techniques — as a continuous discipline for managing technical debt, closely paired with test-driven-development.
Root Cause Analysis — Use when asked to investigate why a problem happened, rather than just its symptoms — the identify/gather-data/analyze/identify-cause/plan/implement steps of root cause analysis (RCA) — used across engineering, manufacturing, healthcare, software, and business management.
Software Architecture — Use when asked to design or explain a single system's high-level structure — components, their responsibilities, and how they interact — as the general discipline underlying specific tools/techniques like arc42, architecture-decision-record, domain-driven-design, and system-quality-attributes.
Software Development Life Cycle — Use when asked to explain or plan around the software development life cycle (SDLC) — Planning, Requirements, Design, Implementation, Testing, Deployment, Maintenance — as the umbrella process this collection's more specific skills (test-driven-development, functional-specification, and others) each occupy one phase of.
Software Engineering — Use when asked to explain software engineering as a general discipline — the engineering practices, processes, and principles applied to building software systems — as distinct from software-engineering-guide (a specific named published guide) and software-engineering-body-of-knowledge (SWEBOK, a specific named standard).
Software Engineering Body of Knowledge — Use when asked about SWEBOK (the Software Engineering Body of Knowledge, published by the IEEE Computer Society) specifically — its knowledge areas — as distinct from the general software-engineering discipline and from a specific published guide like software-engineering-guide.
Software Engineering Guide — Use when the user wants software engineering best-practice guidance grounded in the Software Engineering Guide, e.g. "what does the guide say about X", "review this against best practices", "how should we handle code review / incident management / API design", or any question about ways of working, programming craft, architecture, security, UI/UX, AI, data, automation, operations, or management. For general readers who want to consult and apply the guide, not to edit it. For editing the guide's own repositories, use software-engineering-guide-maintainer instead.
Software Engineering Metrics — Use when someone wants to apply this book's guidance to their own team or organization -- choosing a metric, naming its gaming vector and guardrail, applying the Flow Framework, SPACE, or DORA, filling in a metrics charter or dashboard spec, or running the maturity self-assessment. Not for editing the book's own chapters; use software-engineering-metrics-maintainer for that.
Speech to Text — Use when asked to add or work with speech-to-text (STT) — transcribing spoken audio into written text, streaming vs. batch transcription, accuracy factors (accents, noise, domain vocabulary) — as the inverse of text-to-speech.
Text to Speech — Use when asked to add or work with text-to-speech (TTS) — synthesizing spoken audio from written text, choosing between neural and concatenative/formant synthesis, SSML for pronunciation/prosody control — as the inverse of speech-to-text.

Technology › Decision records 2

Architecture Decision Record — Use when a user wants to create, write, name, place, or organize an Architecture Decision Record (ADR) in a software project — e.g. "write an ADR for choosing a database", "document this architecture decision", "set up an adr/ or decisions/ directory", "which ADR template should I use", "supersede an old ADR". Covers picking a template, naming the file, filling in context/decision/consequences, and deciding whether a decision even needs an ADR.
Decision Records — Draft, review, and manage decision records (DRs) — short documents that capture one significant choice, its context, the options considered, the decision, and its consequences. Use when someone wants to write a decision record or ADR, decide whether a choice is significant enough to warrant one, pick between a lightweight and a comprehensive template, walk through drafting one step by step, find a worked example close to their own domain, or check a draft before publishing it for comment.

Technology › Cloud 5

AWS Cloud — Use when asked to write or debug AWS infrastructure (CLI, CloudFormation/CDK/Terraform against AWS), choose a compute/storage/database service, configure IAM, or explain AWS-specific concepts (regions/AZs, VPCs, the shared responsibility model) — independent of any specific application framework.
Azure Cloud — Use when asked to write or debug Microsoft Azure infrastructure (Azure CLI, ARM/Bicep/Terraform against Azure), choose a compute/storage/database service, configure Azure AD/RBAC, or explain Azure-specific concepts (resource groups, subscriptions, management groups) — independent of any specific application framework.
Civo Cloud — Use when asked what Civo is, how to use its Kubernetes/compute/storage products (public or sovereign private cloud), or how it compares to other cloud providers. Verify current regions/products/pricing against civo.com before repeating specifics from this file — captured from the site on 2026-09-05.
Google Cloud — Use when asked to write or debug Google Cloud Platform (GCP) infrastructure (gcloud CLI, Terraform against GCP), choose a compute/storage/database service, configure IAM, or explain GCP-specific concepts (projects, resource hierarchy, VPCs) — independent of any specific application framework.
Scaleway Cloud — Use when asked what Scaleway is, how to use its compute/Kubernetes/storage/GPU products, or how it compares to AWS/GCP/Azure — a European, sovereignty-focused cloud provider. Verify current regions/products/pricing at scaleway.com before repeating specifics from this file — captured from the site on 2026-09-05.

Technology › Version control 4

Codeberg — Use when asked about Codeberg-specific features — a non-profit, Forgejo-based git hosting platform — pull requests, Codeberg/Forgejo Actions, or why a project mirrors to Codeberg alongside GitHub/GitLab. As opposed to git itself (see git) or the other major hosting platforms (see github, gitlab).
Git — Use when asked to write or explain git commands, resolve a merge conflict, choose a branching strategy, or understand git internals (commits, refs, the index, rebase vs merge) — independent of any specific hosting platform (GitHub/GitLab/Codeberg).
Github — Use when asked about GitHub-specific features — pull requests, GitHub Actions, Issues, the gh CLI, branch protection, or GitHub Pages — as opposed to git itself (see git) or another hosting platform (see gitlab, codeberg).
Gitlab — Use when asked about GitLab-specific features — merge requests, GitLab CI/CD pipelines, the glab CLI, or self-hosted GitLab — as opposed to git itself (see git) or another hosting platform (see github, codeberg).

Technology › Design & UX 10

Anticipatory Design — Use when asked to design a UX that predicts and fulfills user needs before they're explicitly expressed — context awareness, predictive analytics, automation, intelligent assistants, adaptive interfaces — as an approach that reduces user decision-making, distinct from user-centred-design's broader discipline.
Copywriting — Use when asked to write persuasive, promotional content — understanding the audience, compelling hooks, the unique selling proposition, persuasive tone, calls to action — as distinct from microcopy's shorter, functional-interface-text focus.
Figma — Use when asked about Figma the design tool — frames, components/variants, auto layout, design tokens/styles, or Dev Mode handoff to code — as opposed to Figma Make (see figma-make), a separate AI prototyping product.
Figma Make — Use when asked what Figma Make is — an AI-powered tool inside Figma for generating interactive prototypes and web apps from natural-language prompts. As opposed to Figma the design tool itself (see figma). Verify current capabilities/availability at figma.com/make before repeating specifics from this file — captured 2026-09-05, and this is a fast-moving product area.
Iconography — Use when asked about the design and use of icons — visual communication, consistency/standards, UX benefits, space optimization, branding, cultural adaptation — as a complementary visual-communication discipline to typography.
Microcopy — Use when asked to write small, functional interface text — labels, instructions, error messages, tooltips, button text — clarity, contextual relevance, user-focused language, tone/voice, error handling — as distinct from copywriting's longer, persuasion-focused content.
Mobile First Design — Use when asked to design or build starting from the smallest screen and scaling up — content/feature prioritization, responsive design, progressive enhancement, mobile-first SEO/indexing — as a design philosophy distinct from responsive design alone.
Site Map — Use when asked to plan or document a website's page hierarchy and navigation structure — sections, links, page hierarchy — for both user navigation/design purposes and machine-readable SEO sitemaps.
Typography — Use when asked about typeface selection and text styling for readability and visual design — typefaces, readability factors, emotional impact, hierarchy, alignment, consistency — for graphic design, web design, and branding.
User Centred Design — Use when asked to apply user-centred design (UCD/UX) methodology — user research methods, personas, journey mapping, usability testing, or the iterative design/test/refine cycle — independent of any specific design tool.

Technology › Internationalization 308

Locale — Use when asked about internationalization (i18n), localization (l10n), locale codes (BCP 47), or how to handle locale-sensitive data (dates, numbers, currency, plurals, text direction) in code — independent of any specific i18n library or framework.
Locale Af 001 — Use when working with the Afrikaans locale (`af-001`) — its endonym Afrikaans, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Af Za — Use when working with the Afrikaans (South Africa) locale (`af-ZA`) — its endonym Afrikaans (Suid-Afrika), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Am 001 — Use when working with the Amharic locale (`am-001`) — its endonym አማርኛ, Ethiopic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Am Et — Use when working with the Amharic (Ethiopia) locale (`am-ET`) — its endonym አማርኛ (ኢትዮጵያ), Ethiopic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar 001 — Use when working with the Arabic locale (`ar-001`) — its endonym العربية, Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Ae — Use when working with the Arabic (United Arab Emirates) locale (`ar-AE`) — its endonym العربية (الإمارات), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Bh — Use when working with the Arabic (Bahrain) locale (`ar-BH`) — its endonym العربية (البحرين), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Dz — Use when working with the Arabic (Algeria) locale (`ar-DZ`) — its endonym العربية (الجزائر), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Eg — Use when working with the Arabic (Egypt) locale (`ar-EG`) — its endonym العربية (مصر), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Iq — Use when working with the Arabic (Iraq) locale (`ar-IQ`) — its endonym العربية (العراق), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Jo — Use when working with the Arabic (Jordan) locale (`ar-JO`) — its endonym العربية (الأردن), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Kw — Use when working with the Arabic (Kuwait) locale (`ar-KW`) — its endonym العربية (الكويت), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Lb — Use when working with the Arabic (Lebanon) locale (`ar-LB`) — its endonym العربية (لبنان), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Ly — Use when working with the Arabic (Libya) locale (`ar-LY`) — its endonym العربية (ليبيا), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Ma — Use when working with the Arabic (Morocco) locale (`ar-MA`) — its endonym العربية (المغرب), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Om — Use when working with the Arabic (Oman) locale (`ar-OM`) — its endonym العربية (عُمان), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Qa — Use when working with the Arabic (Qatar) locale (`ar-QA`) — its endonym العربية (قطر), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Sa — Use when working with the Arabic (Saudi Arabia) locale (`ar-SA`) — its endonym العربية (السعودية), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Sd — Use when working with the Arabic (Sudan) locale (`ar-SD`) — its endonym العربية (السودان), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Sy — Use when working with the Arabic (Syria) locale (`ar-SY`) — its endonym العربية (سوريا), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Tn — Use when working with the Arabic (Tunisia) locale (`ar-TN`) — its endonym العربية (تونس), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ar Ye — Use when working with the Arabic (Yemen) locale (`ar-YE`) — its endonym العربية (اليمن), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Arn Cl — Use when working with the Mapudungun (Chile) locale (`arn-CL`) — its endonym Mapudungun (Chile), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale As 001 — Use when working with the Assamese locale (`as-001`) — its endonym অসমীয়া, Bengali script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale As in — Use when working with the Assamese (India) locale (`as-IN`) — its endonym অসমীয়া (ভাৰত), Bengali script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Az 001 — Use when working with the Azerbaijani locale (`az-001`) — its endonym Azərbaycan dili, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ba Ru — Use when working with the Bashkir (Russia) locale (`ba-RU`) — its endonym Башҡорт теле (Россия), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Be 001 — Use when working with the Belarusian locale (`be-001`) — its endonym Беларуская, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Be By — Use when working with the Belarusian (Belarus) locale (`be-BY`) — its endonym Беларуская (Беларусь), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bg 001 — Use when working with the Bulgarian locale (`bg-001`) — its endonym Български, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bg Bg — Use when working with the Bulgarian (Bulgaria) locale (`bg-BG`) — its endonym Български (България), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bh 001 — Use when working with the Bhojpuri locale (`bh-001`) — its endonym भोजपुरी, Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bn 001 — Use when working with the Bengali locale (`bn-001`) — its endonym বাংলা, Bengali script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bn Bd — Use when working with the Bengali (Bangladesh) locale (`bn-BD`) — its endonym বাংলা (বাংলাদেশ), Bengali script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bn in — Use when working with the Bengali (India) locale (`bn-IN`) — its endonym বাংলা (ভারত), Bengali script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bo 001 — Use when working with the Tibetan locale (`bo-001`) — its endonym བོད་སྐད་, Tibetan script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bo Cn — Use when working with the Tibetan (China) locale (`bo-CN`) — its endonym བོད་སྐད་ (ཀྲུང་གོ), Tibetan script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Br Fr — Use when working with the Breton (France) locale (`br-FR`) — its endonym Brezhoneg (Frañs), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Bs 001 — Use when working with the Bosnian locale (`bs-001`) — its endonym Bosanski, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ca Es — Use when working with the Catalan (Spain) locale (`ca-ES`) — its endonym Català (Espanya), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Co 001 — Use when working with the Corsican locale (`co-001`) — its endonym Corsu, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Co Fr — Use when working with the Corsican (France) locale (`co-FR`) — its endonym Corsu (Francia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Cs 001 — Use when working with the Czech locale (`cs-001`) — its endonym Čeština, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Cs Cz — Use when working with the Czech (Czech Republic) locale (`cs-CZ`) — its endonym Čeština (Česko), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Cy 001 — Use when working with the Welsh locale (`cy-001`) — its endonym Cymraeg, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Cy Gb — Use when working with the Welsh (United Kingdom) locale (`cy-GB`) — its endonym Cymraeg (y Deyrnas Unedig), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Da 001 — Use when working with the Danish locale (`da-001`) — its endonym Dansk, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Da Dk — Use when working with the Danish (Denmark) locale (`da-DK`) — its endonym Dansk (Danmark), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale De 001 — Use when working with the German locale (`de-001`) — its endonym Deutsch, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale De At — Use when working with the German (Austria) locale (`de-AT`) — its endonym Deutsch (Österreich), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale De Ch — Use when working with the German (Switzerland) locale (`de-CH`) — its endonym Deutsch (Schweiz), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale De De — Use when working with the German (Germany) locale (`de-DE`) — its endonym Deutsch (Deutschland), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale De Li — Use when working with the German (Liechtenstein) locale (`de-LI`) — its endonym Deutsch (Liechtenstein), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale De Lu — Use when working with the German (Luxembourg) locale (`de-LU`) — its endonym Deutsch (Luxemburg), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Dsb De — Use when working with the Lower Sorbian (Germany) locale (`dsb-DE`) — its endonym Dolnoserbšćina (Nimska), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Dv Mv — Use when working with the Divehi (Maldives) locale (`dv-MV`) — its endonym ދިވެހި (ދިވެހިރާއްޖެ), Thaana script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale El 001 — Use when working with the Greek locale (`el-001`) — its endonym Ελληνικά, Greek script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale El Cy — Use when working with the Greek (Cyprus) locale (`el-CY`) — its endonym Ελληνικά (Κύπρος), Greek script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale El Gr — Use when working with the Greek (Greece) locale (`el-GR`) — its endonym Ελληνικά (Ελλάδα), Greek script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En 001 — Use when working with the English locale (`en-001`) — its endonym English, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En 150 — Use when working with the English (Europe) locale (`en-150`) — its endonym English (Europe), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Au — Use when working with the English (Australia) locale (`en-AU`) — its endonym English (Australia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Bz — Use when working with the English (Belize) locale (`en-BZ`) — its endonym English (Belize), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Ca — Use when working with the English (Canada) locale (`en-CA`) — its endonym English (Canada), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Gb — Use when working with the English (Great Britain) locale (`en-GB`) — its endonym English (Great Britain), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Ie — Use when working with the English (Ireland) locale (`en-IE`) — its endonym English (Ireland), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En in — Use when working with the English (India) locale (`en-IN`) — its endonym English (India), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Jm — Use when working with the English (Jamaica) locale (`en-JM`) — its endonym English (Jamaica), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Mt — Use when working with the English (Malta) locale (`en-MT`) — its endonym English (Malta), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En My — Use when working with the English (Malaysia) locale (`en-MY`) — its endonym English (Malaysia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Nz — Use when working with the English (New Zealand) locale (`en-NZ`) — its endonym English (New Zealand), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Ph — Use when working with the English (Philippines) locale (`en-PH`) — its endonym English (Philippines), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Sg — Use when working with the English (Singapore) locale (`en-SG`) — its endonym English (Singapore), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Tt — Use when working with the English (Trinidad and Tobago) locale (`en-TT`) — its endonym English (Trinidad and Tobago), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Us — Use when working with the English (United States) locale (`en-US`) — its endonym English (United States), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Za — Use when working with the English (South Africa) locale (`en-ZA`) — its endonym English (South Africa), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale En Zw — Use when working with the English (Zimbabwe) locale (`en-ZW`) — its endonym English (Zimbabwe), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Eo 001 — Use when working with the Esperanto locale (`eo-001`) — its endonym Esperanto, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es 001 — Use when working with the Spanish locale (`es-001`) — its endonym Español, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es 419 — Use when working with the Spanish (Latin America) locale (`es-419`) — its endonym Español (Latinoamérica), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Ar — Use when working with the Spanish (Argentina) locale (`es-AR`) — its endonym Español (Argentina), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Bo — Use when working with the Spanish (Bolivia) locale (`es-BO`) — its endonym Español (Bolivia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Cl — Use when working with the Spanish (Chile) locale (`es-CL`) — its endonym Español (Chile), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Co — Use when working with the Spanish (Colombia) locale (`es-CO`) — its endonym Español (Colombia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Cr — Use when working with the Spanish (Costa Rica) locale (`es-CR`) — its endonym Español (Costa Rica), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Do — Use when working with the Spanish (Dominican Republic) locale (`es-DO`) — its endonym Español (República Dominicana), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Ec — Use when working with the Spanish (Ecuador) locale (`es-EC`) — its endonym Español (Ecuador), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Es — Use when working with the Spanish (Spain) locale (`es-ES`) — its endonym Español (España), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Gt — Use when working with the Spanish (Guatemala) locale (`es-GT`) — its endonym Español (Guatemala), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Hn — Use when working with the Spanish (Honduras) locale (`es-HN`) — its endonym Español (Honduras), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Mx — Use when working with the Spanish (Mexico) locale (`es-MX`) — its endonym Español (México), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Ni — Use when working with the Spanish (Nicaragua) locale (`es-NI`) — its endonym Español (Nicaragua), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Pa — Use when working with the Spanish (Panama) locale (`es-PA`) — its endonym Español (Panamá), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Pe — Use when working with the Spanish (Peru) locale (`es-PE`) — its endonym Español (Perú), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Pr — Use when working with the Spanish (Puerto Rico) locale (`es-PR`) — its endonym Español (Puerto Rico), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Py — Use when working with the Spanish (Paraguay) locale (`es-PY`) — its endonym Español (Paraguay), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Sv — Use when working with the Spanish (El Salvador) locale (`es-SV`) — its endonym Español (El Salvador), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Us — Use when working with the Spanish (United States) locale (`es-US`) — its endonym Español (Estados Unidos), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Uy — Use when working with the Spanish (Uruguay) locale (`es-UY`) — its endonym Español (Uruguay), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Es Ve — Use when working with the Spanish (Venezuela) locale (`es-VE`) — its endonym Español (Venezuela), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Et 001 — Use when working with the Estonian locale (`et-001`) — its endonym Eesti, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Et Ee — Use when working with the Estonian (Estonia) locale (`et-EE`) — its endonym Eesti (Eesti), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Eu 001 — Use when working with the Basque locale (`eu-001`) — its endonym Euskara, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Eu Es — Use when working with the Basque (Spain) locale (`eu-ES`) — its endonym Euskara (Espainia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fa 001 — Use when working with the Persian locale (`fa-001`) — its endonym فارسی, Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fa Ir — Use when working with the Persian (Iran) locale (`fa-IR`) — its endonym فارسی (ایران), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fi 001 — Use when working with the Finnish locale (`fi-001`) — its endonym Suomi, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fi Fi — Use when working with the Finnish (Finland) locale (`fi-FI`) — its endonym Suomi (Suomi), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fil 001 — Use when working with the Filipino locale (`fil-001`) — its endonym Filipino, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fil Ph — Use when working with the Filipino (Philippines) locale (`fil-PH`) — its endonym Filipino (Pilipinas), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fo Fo — Use when working with the Faroese (Faroe Islands) locale (`fo-FO`) — its endonym Føroyskt (Føroyar), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fr 001 — Use when working with the French locale (`fr-001`) — its endonym Français, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fr Be — Use when working with the French (Belgium) locale (`fr-BE`) — its endonym Français (Belgique), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fr Ca — Use when working with the French (Canada) locale (`fr-CA`) — its endonym Français (Le Canada), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fr Ch — Use when working with the French (Switzerland) locale (`fr-CH`) — its endonym Français (Suisse), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fr Fr — Use when working with the French (France) locale (`fr-FR`) — its endonym Français (La France), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fr Lu — Use when working with the French (Luxembourg) locale (`fr-LU`) — its endonym Français (Luxembourg), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fr Mc — Use when working with the French (Monaco) locale (`fr-MC`) — its endonym Français (Monaco), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fy 001 — Use when working with the Frisian locale (`fy-001`) — its endonym Frysk, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Fy Nl — Use when working with the Frisian (Netherlands) locale (`fy-NL`) — its endonym Frysk (Nederlân), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ga 001 — Use when working with the Irish locale (`ga-001`) — its endonym Gaeilge, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ga Ie — Use when working with the Irish (Ireland) locale (`ga-IE`) — its endonym Gaeilge (Éire), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Gd 001 — Use when working with the Scottish Gaelic locale (`gd-001`) — its endonym Gàidhlig, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Gd Gb — Use when working with the Scottish Gaelic (United Kingdom) locale (`gd-GB`) — its endonym Gàidhlig (An Rìoghachd Aonaichte), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Gl Es — Use when working with the Galician (Spain) locale (`gl-ES`) — its endonym Galego (España), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Gsw Fr — Use when working with the Alsatian (France) locale (`gsw-FR`) — its endonym Elsässisch (Frankreich), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Gu 001 — Use when working with the Gujarati locale (`gu-001`) — its endonym ગુજરાતી, Gujarati script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ha 001 — Use when working with the Hausa locale (`ha-001`) — its endonym Harshen Hausa, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ha Ng — Use when working with the Hausa (Nigeria) locale (`ha-NG`) — its endonym Harshen Hausa (Najeriya), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale He 001 — Use when working with the Hebrew locale (`he-001`) — its endonym עברית, Hebrew script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale He Il — Use when working with the Hebrew (Israel) locale (`he-IL`) — its endonym עברית (ישראל), Hebrew script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hi 001 — Use when working with the Hindi locale (`hi-001`) — its endonym हिन्दी, Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hi in — Use when working with the Hindi (India) locale (`hi-IN`) — its endonym हिन्दी (भारत), Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hr 001 — Use when working with the Croatian locale (`hr-001`) — its endonym Hrvatski, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hr Ba — Use when working with the Croatian (Bosnia and Herzegovina) locale (`hr-BA`) — its endonym Hrvatski (Bosna i Hercegovina), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hr Hr — Use when working with the Croatian (Croatia) locale (`hr-HR`) — its endonym Hrvatski (Hrvatska), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hsb De — Use when working with the Upper Sorbian (Germany) locale (`hsb-DE`) — its endonym Hornjoserbšćina (Němska), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hu 001 — Use when working with the Hungarian locale (`hu-001`) — its endonym Magyar, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hu Hu — Use when working with the Hungarian (Hungary) locale (`hu-HU`) — its endonym Magyar (Magyarország), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hy 001 — Use when working with the Armenian locale (`hy-001`) — its endonym Հայերեն, Armenian script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Hy Am — Use when working with the Armenian (Armenia) locale (`hy-AM`) — its endonym Հայերեն (Հայաստան), Armenian script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Id 001 — Use when working with the Indonesian locale (`id-001`) — its endonym Bahasa Indonesia, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Id Id — Use when working with the Indonesian (Indonesia) locale (`id-ID`) — its endonym Bahasa Indonesia (Indonesia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ig 001 — Use when working with the Igbo locale (`ig-001`) — its endonym Igbo, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ig Ng — Use when working with the Igbo (Nigeria) locale (`ig-NG`) — its endonym Igbo (Naịjịrịa), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ii Cn — Use when working with the Yi (China) locale (`ii-CN`) — its endonym ꆈꌠꉙ (ꍏꉸ), Yi script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Is 001 — Use when working with the Icelandic locale (`is-001`) — its endonym Íslenska, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Is Is — Use when working with the Icelandic (Iceland) locale (`is-IS`) — its endonym Íslenska (Ísland), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale It 001 — Use when working with the Italian locale (`it-001`) — its endonym Italiano, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale It Ch — Use when working with the Italian (Switzerland) locale (`it-CH`) — its endonym Italiano (Svizzera), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale It It — Use when working with the Italian (Italy) locale (`it-IT`) — its endonym Italiano (Italia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ja 001 — Use when working with the Japanese locale (`ja-001`) — its endonym 日本語, Japanese script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ja Jp — Use when working with the Japanese (Japan) locale (`ja-JP`) — its endonym 日本語 (日本), Japanese script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Jv 001 — Use when working with the Javanese locale (`jv-001`) — its endonym Basa Jawa, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ka 001 — Use when working with the Georgian locale (`ka-001`) — its endonym ქართული, Georgian script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ka Ge — Use when working with the Georgian (Georgia) locale (`ka-GE`) — its endonym ქართული (საქართველო), Georgian script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Kk 001 — Use when working with the Kazakh locale (`kk-001`) — its endonym Қазақ тілі, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Kk Kz — Use when working with the Kazakh (Kazakhstan) locale (`kk-KZ`) — its endonym Қазақ тілі (Қазақстан), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Kl Gl — Use when working with the Greenlandic (Greenland) locale (`kl-GL`) — its endonym Kalaallisut (Kalaallit Nunaat), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Km 001 — Use when working with the Khmer locale (`km-001`) — its endonym ខ្មែរ, Khmer script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Km Kh — Use when working with the Khmer (Cambodia) locale (`km-KH`) — its endonym ខ្មែរ (កម្ពុជា), Khmer script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Kn 001 — Use when working with the Kannada locale (`kn-001`) — its endonym ಕನ್ನಡ, Kannada script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Kn in — Use when working with the Kannada (India) locale (`kn-IN`) — its endonym ಕನ್ನಡ (ಭಾರತ), Kannada script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ko 001 — Use when working with the Korean locale (`ko-001`) — its endonym 한국어, Korean script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ko Kr — Use when working with the Korean (Korea) locale (`ko-KR`) — its endonym 한국어 (대한민국), Korean script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Kok in — Use when working with the Konkani (India) locale (`kok-IN`) — its endonym कोंकणी (भारत), Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ku 001 — Use when working with the Kurdish locale (`ku-001`) — its endonym Kurdî, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ky 001 — Use when working with the Kyrgyz locale (`ky-001`) — its endonym Кыргызча, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ky Kg — Use when working with the Kyrgyz (Kyrgyzstan) locale (`ky-KG`) — its endonym Кыргызча (Кыргызстан), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale La 001 — Use when working with the Latin locale (`la-001`) — its endonym Latina, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Lb 001 — Use when working with the Luxembourgish locale (`lb-001`) — its endonym Lëtzebuergesch, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Lb Lu — Use when working with the Luxembourgish (Luxembourg) locale (`lb-LU`) — its endonym Lëtzebuergesch (Lëtzebuerg), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Lo 001 — Use when working with the Lao locale (`lo-001`) — its endonym ລາວ, Lao script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Lo La — Use when working with the Lao (Laos) locale (`lo-LA`) — its endonym ລາວ (ລາວ), Lao script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Lt 001 — Use when working with the Lithuanian locale (`lt-001`) — its endonym Lietuvių, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Lt Lt — Use when working with the Lithuanian (Lithuania) locale (`lt-LT`) — its endonym Lietuvių (Lietuva), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Lv 001 — Use when working with the Latvian locale (`lv-001`) — its endonym Latviešu, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Lv Lv — Use when working with the Latvian (Latvia) locale (`lv-LV`) — its endonym Latviešu (Latvija), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mg 001 — Use when working with the Malagasy locale (`mg-001`) — its endonym Malagasy, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mi 001 — Use when working with the Maori locale (`mi-001`) — its endonym Māori, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mi Nz — Use when working with the Maori (New Zealand) locale (`mi-NZ`) — its endonym Māori (Aotearoa), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mk 001 — Use when working with the Macedonian locale (`mk-001`) — its endonym Македонски, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mk Mk — Use when working with the Macedonian (North Macedonia) locale (`mk-MK`) — its endonym Македонски (Северна Македонија), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ml 001 — Use when working with the Malayalam locale (`ml-001`) — its endonym മലയാളം, Malayalam script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ml in — Use when working with the Malayalam (India) locale (`ml-IN`) — its endonym മലയാളം (ഭാരതം), Malayalam script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mn 001 — Use when working with the Mongolian locale (`mn-001`) — its endonym Монгол, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mn Mn — Use when working with the Mongolian (Mongolia) locale (`mn-MN`) — its endonym Монгол (Монгол улс), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Moh Ca — Use when working with the Mohawk (Canada) locale (`moh-CA`) — its endonym Kanien'kéha (Kanata), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mr 001 — Use when working with the Marathi locale (`mr-001`) — its endonym मराठी, Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mr in — Use when working with the Marathi (India) locale (`mr-IN`) — its endonym मराठी (भारत), Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ms 001 — Use when working with the Malay locale (`ms-001`) — its endonym Bahasa Melayu, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ms Bn — Use when working with the Malay (Brunei) locale (`ms-BN`) — its endonym Bahasa Melayu (Brunei), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ms My — Use when working with the Malay (Malaysia) locale (`ms-MY`) — its endonym Bahasa Melayu (Malaysia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mt 001 — Use when working with the Maltese locale (`mt-001`) — its endonym Malti, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Mt Mt — Use when working with the Maltese (Malta) locale (`mt-MT`) — its endonym Malti (Malta), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale My 001 — Use when working with the Burmese locale (`my-001`) — its endonym မြန်မာစာ, Myanmar script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Nb No — Use when working with the Norwegian Bokmål (Norway) locale (`nb-NO`) — its endonym Norsk Bokmål (Norge), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ne 001 — Use when working with the Nepali locale (`ne-001`) — its endonym नेपाली, Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ne Np — Use when working with the Nepali (Nepal) locale (`ne-NP`) — its endonym नेपाली (नेपाल), Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Nl 001 — Use when working with the Dutch locale (`nl-001`) — its endonym Nederlands, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Nl Be — Use when working with the Dutch (Belgium) locale (`nl-BE`) — its endonym Nederlands (België), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Nl Nl — Use when working with the Dutch (Netherlands) locale (`nl-NL`) — its endonym Nederlands (Nederland), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Nn No — Use when working with the Norwegian Nynorsk (Norway) locale (`nn-NO`) — its endonym Norsk Nynorsk (Noreg), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale No 001 — Use when working with the Norwegian locale (`no-001`) — its endonym Norsk, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Nso Za — Use when working with the Northern Sotho (South Africa) locale (`nso-ZA`) — its endonym Sesotho sa Leboa (Afrika Borwa), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ny 001 — Use when working with the Chichewa locale (`ny-001`) — its endonym Chichewa, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Oc Fr — Use when working with the Occitan (France) locale (`oc-FR`) — its endonym Occitan (França), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale or 001 — Use when working with the Odia locale (`or-001`) — its endonym ଓଡ଼ିଆ, Oriya script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale or in — Use when working with the Odia (India) locale (`or-IN`) — its endonym ଓଡ଼ିଆ (ଭାରତ), Oriya script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Pa 001 — Use when working with the Punjabi locale (`pa-001`) — its endonym ਪੰਜਾਬੀ, Gurmukhi script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Pa in — Use when working with the Punjabi (India) locale (`pa-IN`) — its endonym ਪੰਜਾਬੀ (ਭਾਰਤ), Gurmukhi script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Pcm 001 — Use when working with the Nigerian Pidgin locale (`pcm-001`) — its endonym Naijá, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Pcm Ng — Use when working with the Nigerian Pidgin (Nigeria) locale (`pcm-NG`) — its endonym Naijá (Nigeria), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Peer Id — Use when asked to track corresponding translated content across locales with a locale peer id, to create or check `.locale-peer-id` files, or to set up a locales directory layout for translation. Distinct from [[locale]], which covers locale codes and locale-sensitive data in code, and from the per-locale skills such as [[locale-en-001]], which give guidance for one locale.
Locale Pl 001 — Use when working with the Polish locale (`pl-001`) — its endonym Polski, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Pl Pl — Use when working with the Polish (Poland) locale (`pl-PL`) — its endonym Polski (Polska), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Prs Af — Use when working with the Dari (Afghanistan) locale (`prs-AF`) — its endonym دری (افغانستان), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ps 001 — Use when working with the Pashto locale (`ps-001`) — its endonym پښتو, Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ps Af — Use when working with the Pashto (Afghanistan) locale (`ps-AF`) — its endonym پښتو (افغانستان), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Pt 001 — Use when working with the Portuguese locale (`pt-001`) — its endonym Português, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Pt Br — Use when working with the Portuguese (Brazil) locale (`pt-BR`) — its endonym Português (O Brasil), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Pt Pt — Use when working with the Portuguese (Portugal) locale (`pt-PT`) — its endonym Português (Portugal), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Quz Bo — Use when working with the Quechua (Bolivia) locale (`quz-BO`) — its endonym Runasimi (Bolivia), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Quz Ec — Use when working with the Quechua (Ecuador) locale (`quz-EC`) — its endonym Runashimi (Ecuador), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Quz Pe — Use when working with the Quechua (Peru) locale (`quz-PE`) — its endonym Runasimi (Perú), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Rm Ch — Use when working with the Romansh (Switzerland) locale (`rm-CH`) — its endonym Rumantsch (Svizra), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ro 001 — Use when working with the Romanian locale (`ro-001`) — its endonym Română, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ro Ro — Use when working with the Romanian (Romania) locale (`ro-RO`) — its endonym Română (România), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ru 001 — Use when working with the Russian locale (`ru-001`) — its endonym Русский, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ru Ru — Use when working with the Russian (Russia) locale (`ru-RU`) — its endonym Русский (Россия), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Rw 001 — Use when working with the Kinyarwanda locale (`rw-001`) — its endonym Ikinyarwanda, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Rw Rw — Use when working with the Kinyarwanda (Rwanda) locale (`rw-RW`) — its endonym Ikinyarwanda (Rwanda), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sa 001 — Use when working with the Sanskrit locale (`sa-001`) — its endonym संस्कृतम्, Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sa in — Use when working with the Sanskrit (India) locale (`sa-IN`) — its endonym संस्कृतम् (भारतम्), Devanagari script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sah Ru — Use when working with the Sakha (Russia) locale (`sah-RU`) — its endonym Саха тыла (Россия), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sd 001 — Use when working with the Sindhi locale (`sd-001`) — its endonym سنڌي, Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Se Fi — Use when working with the Northern Sami (Finland) locale (`se-FI`) — its endonym Davvisámegiella (Suoma), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Se No — Use when working with the Northern Sami (Norway) locale (`se-NO`) — its endonym Davvisámegiella (Norga), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Se Se — Use when working with the Northern Sami (Sweden) locale (`se-SE`) — its endonym Davvisámegiella (Ruoŧŧa), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Si 001 — Use when working with the Sinhala locale (`si-001`) — its endonym සිංහල, Sinhala script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Si Lk — Use when working with the Sinhala (Sri Lanka) locale (`si-LK`) — its endonym සිංහල (ශ්‍රී ලංකාව), Sinhala script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sk 001 — Use when working with the Slovak locale (`sk-001`) — its endonym Slovenčina, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sk Sk — Use when working with the Slovak (Slovakia) locale (`sk-SK`) — its endonym Slovenčina (Slovensko), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sl 001 — Use when working with the Slovenian locale (`sl-001`) — its endonym Slovenščina, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sl Si — Use when working with the Slovenian (Slovenia) locale (`sl-SI`) — its endonym Slovenščina (Slovenija), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sm 001 — Use when working with the Samoan locale (`sm-001`) — its endonym Gagana Sāmoa, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sma No — Use when working with the Southern Sami (Norway) locale (`sma-NO`) — its endonym Åarjelsaemien gïele (Nöörje), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sma Se — Use when working with the Southern Sami (Sweden) locale (`sma-SE`) — its endonym Åarjelsaemien gïele (Sveerje), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Smj No — Use when working with the Lule Sami (Norway) locale (`smj-NO`) — its endonym Julevsámegiella (Vuodna), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Smj Se — Use when working with the Lule Sami (Sweden) locale (`smj-SE`) — its endonym Julevsámegiella (Svierik), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Smn Fi — Use when working with the Inari Sami (Finland) locale (`smn-FI`) — its endonym Anarâškielâ (Suomâ), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sms Fi — Use when working with the Skolt Sami (Finland) locale (`sms-FI`) — its endonym Sääʹmǩiõll (Lääʹdd), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sn 001 — Use when working with the Shona locale (`sn-001`) — its endonym chiShona, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale So 001 — Use when working with the Somali locale (`so-001`) — its endonym Soomaali, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sq 001 — Use when working with the Albanian locale (`sq-001`) — its endonym Shqip, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sq Al — Use when working with the Albanian (Albania) locale (`sq-AL`) — its endonym Shqip (Shqipëri), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sr 001 — Use when working with the Serbian locale (`sr-001`) — its endonym Српски, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sr Ba — Use when working with the Serbian (Bosnia and Herzegovina) locale (`sr-BA`) — its endonym Српски (Босна и Херцеговина), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sr Me — Use when working with the Serbian (Montenegro) locale (`sr-ME`) — its endonym Српски (Црна Гора), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sr Rs — Use when working with the Serbian (Serbia) locale (`sr-RS`) — its endonym Српски (Србија), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale St 001 — Use when working with the Sesotho locale (`st-001`) — its endonym Sesotho, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sv 001 — Use when working with the Swedish locale (`sv-001`) — its endonym Svenska, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sv Fi — Use when working with the Swedish (Finland) locale (`sv-FI`) — its endonym Svenska (Finland), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sv Se — Use when working with the Swedish (Sweden) locale (`sv-SE`) — its endonym Svenska (Sverige), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sw 001 — Use when working with the Swahili locale (`sw-001`) — its endonym Kiswahili, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sw Ke — Use when working with the Swahili (Kenya) locale (`sw-KE`) — its endonym Kiswahili (Kenya), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Sw Tz — Use when working with the Swahili (Tanzania) locale (`sw-TZ`) — its endonym Kiswahili (Tanzania), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Syr Sy — Use when working with the Syriac (Syria) locale (`syr-SY`) — its endonym ܣܘܪܝܝܐ (ܣܘܪܝܐ), Syriac script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ta 001 — Use when working with the Tamil locale (`ta-001`) — its endonym தமிழ், Tamil script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ta in — Use when working with the Tamil (India) locale (`ta-IN`) — its endonym தமிழ் (இந்தியா), Tamil script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Te 001 — Use when working with the Telugu locale (`te-001`) — its endonym తెలుగు, Telugu script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Te in — Use when working with the Telugu (India) locale (`te-IN`) — its endonym తెలుగు (భారత దేశం), Telugu script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Tg 001 — Use when working with the Tajik locale (`tg-001`) — its endonym Тоҷикӣ, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Th 001 — Use when working with the Thai locale (`th-001`) — its endonym ไทย, Thai script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Th Th — Use when working with the Thai (Thailand) locale (`th-TH`) — its endonym ไทย (ไทย), Thai script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ti 001 — Use when working with the Tigrinya locale (`ti-001`) — its endonym ትግርኛ, Ethiopic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Tk 001 — Use when working with the Turkmen locale (`tk-001`) — its endonym Türkmençe, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Tk Tm — Use when working with the Turkmen (Turkmenistan) locale (`tk-TM`) — its endonym Türkmençe (Türkmenistan), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Tn Za — Use when working with the Tswana (South Africa) locale (`tn-ZA`) — its endonym Setswana (Aforika Borwa), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Tr 001 — Use when working with the Turkish locale (`tr-001`) — its endonym Türkçe, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Tr Tr — Use when working with the Turkish (Turkey) locale (`tr-TR`) — its endonym Türkçe (Türkiye), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Tt 001 — Use when working with the Tatar locale (`tt-001`) — its endonym Татар теле, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Tt Ru — Use when working with the Tatar (Russia) locale (`tt-RU`) — its endonym Татар теле (Россия), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ug 001 — Use when working with the Uyghur locale (`ug-001`) — its endonym ئۇيغۇرچە, Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ug Cn — Use when working with the Uyghur (China) locale (`ug-CN`) — its endonym ئۇيغۇرچە (جۇڭگو), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Uk 001 — Use when working with the Ukrainian locale (`uk-001`) — its endonym Українська, Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Uk Ua — Use when working with the Ukrainian (Ukraine) locale (`uk-UA`) — its endonym Українська (Україна), Cyrillic script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ur 001 — Use when working with the Urdu locale (`ur-001`) — its endonym اردو, Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Ur Pk — Use when working with the Urdu (Pakistan) locale (`ur-PK`) — its endonym اردو (پاکستان), Arabic script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Uz 001 — Use when working with the Uzbek locale (`uz-001`) — its endonym Oʻzbekcha, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Vi 001 — Use when working with the Vietnamese locale (`vi-001`) — its endonym Tiếng Việt, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Vi Vn — Use when working with the Vietnamese (Vietnam) locale (`vi-VN`) — its endonym Tiếng Việt (Việt Nam), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Wo Sn — Use when working with the Wolof (Senegal) locale (`wo-SN`) — its endonym Wolof (Senegaal), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Xh 001 — Use when working with the Xhosa locale (`xh-001`) — its endonym isiXhosa, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Xh Za — Use when working with the Xhosa (South Africa) locale (`xh-ZA`) — its endonym isiXhosa (uMzantsi Afrika), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Yi 001 — Use when working with the Yiddish locale (`yi-001`) — its endonym ייִדיש, Hebrew script, right-to-left (RTL) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Yo 001 — Use when working with the Yoruba locale (`yo-001`) — its endonym Yorùbá, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Yo Ng — Use when working with the Yoruba (Nigeria) locale (`yo-NG`) — its endonym Yorùbá (Nàìjíríà), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Zh 001 — Use when working with the Chinese locale (`zh-001`) — its endonym 普通话, Han (Simplified) script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Zh Cn — Use when working with the Chinese (Simplified, China) locale (`zh-CN`) — its endonym 简体中文 (中国), Han (Simplified) script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Zh Hk — Use when working with the Chinese (Traditional, Hong Kong) locale (`zh-HK`) — its endonym 繁體中文 (香港), Han (Traditional) script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Zh Mo — Use when working with the Chinese (Traditional, Macao) locale (`zh-MO`) — its endonym 繁體中文 (澳門), Han (Traditional) script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Zh Sg — Use when working with the Chinese (Simplified, Singapore) locale (`zh-SG`) — its endonym 简体中文 (新加坡), Han (Simplified) script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Zh Tw — Use when working with the Chinese (Traditional, Taiwan) locale (`zh-TW`) — its endonym 繁體中文 (台灣), Han (Traditional) script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Zu 001 — Use when working with the Zulu locale (`zu-001`) — its endonym isiZulu, Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Locale Zu Za — Use when working with the Zulu (South Africa) locale (`zu-ZA`) — its endonym isiZulu (iNingizimu Afrika), Latin script, left-to-right (LTR) direction, or spoken-population data. Reference data and translation guidance (register, grammar, idiom, typography) for this specific locale; see [[locale]] for general i18n/l10n concepts (BCP 47, plural rules, RTL) that apply across all locales.
Unicode Messageformat — Use when reading, writing, or debugging Unicode MessageFormat 2 (MF2) message syntax — the Unicode Consortium's standard for localizable messages with placeholders, plural/selection matching, and formatting functions. Independent of any library; see [[sveltia-i18n]] for a Svelte library built on it and [[locale]] for broader i18n/l10n concepts.

Technology › Software development practices 6

Behavior Driven Development — Use when asked to write Given/When/Then scenarios, Gherkin feature files, or explain behavior-driven development (BDD) — as distinct from test-driven development's red/green/refactor cycle (see test-driven-development), which BDD layers a shared-language discipline on top of.
Code Review Checklist — Use when asked to create or apply a code review checklist — a structured set of things a reviewer checks on a code change (correctness, tests, readability, security, scope) — to keep reviews consistent across reviewers rather than dependent on whoever happens to review, as distinct from [[refactoring]], which is the act of restructuring code rather than evaluating someone else's change.
Pair Programming — Use when asked to set up or run pair programming — driver/navigator roles, in-person and remote setups — as a real-time collaborative alternative to solo development plus asynchronous code review, and a common practice alongside test-driven-development.
Specification Driven Development — Use when asked to write a spec before implementation, structure a spec-first repository (spec/index.md, per-topic specs), or explain specification-driven development — as distinct from test-driven development (see test-driven-development), which drives design from tests rather than a written specification document.
Technical Debt Register — Use when asked to create or maintain a technical debt register — a tracked, visible list of known shortcuts, deferred fixes, and code needing rework — so debt is a deliberate, chosen tradeoff rather than something invisible until it causes a problem, as distinct from [[refactoring]], which is the act of paying down debt rather than tracking that it exists.
Test Driven Development — Use when asked to write code test-driven — red/green/refactor, writing the failing test first, or explaining TDD's benefits and limits — as distinct from behavior-driven development's given/when/then framing (see behavior-driven-development) or writing tests after the fact.

Technology › Documentation 4

API Documentation — Use when asked to write or improve API documentation — reference docs for a REST, GraphQL, or SDK interface covering authentication, endpoints or methods, parameters, return values, and error codes — as distinct from [[readme-writing]], which orients a newcomer to a whole project rather than documenting one interface in depth.
Changelog — Use when asked to write or maintain a changelog — the complete, running, human-readable record of notable changes to a project across all versions — as distinct from [[release-notes]], which is the announcement for one specific release, narrower in scope and often more promotional in tone.
README Writing — Use when asked to write or improve a project's README — the first, and often only, file a visitor reads to understand what a project is, whether it's relevant, and how to start using it — as distinct from [[api-documentation]], which documents a specific interface's operations in depth rather than orienting a newcomer to the whole project.
Release Notes — Use when asked to write release notes — the announcement accompanying one specific release, aimed at users deciding whether and how it affects them — as distinct from a [[changelog]], which is the complete, cumulative running history across every version rather than one release's announcement.

Technology › Diagramming 20

Activity Diagram — Use when asked to model a workflow or business process as a UML activity diagram — activities, transitions, decisions, and swimlanes — as distinct from a state diagram (see state-diagram), which models one object's states rather than a flow of actions. See plantuml for the text-based syntax to actually draw one.
Cause and Effect Diagram — Use when asked to run a root-cause analysis session using a fishbone/Ishikawa-style diagram — the 6M cause categories (Manpower, Methods, Machines, Materials, Measurements, Mother Nature) — the same technique also called fishbone-diagram or ishikawa-diagram under alternate names.
Class Diagram — Use when asked to model a system's static structure as a UML class diagram — classes, attributes, methods, and association/aggregation/composition relationships — as the type-level counterpart to an object diagram's instance snapshot (see object-diagram). See plantuml for the text-based syntax to actually draw one.
Component Diagram — Use when asked to model a system's software architecture as interacting components — dependency, association, aggregation, composition between components — as distinct from a deployment diagram's runtime hardware/node view (see deployment-diagram), which shows where components run rather than how they relate to each other.
Deployment Diagram — Use when asked to model the physical/runtime architecture of a distributed system — nodes, components, artifacts — as the runtime-placement counterpart to a component diagram's logical software relationships (see component-diagram). See plantuml for the text-based syntax to actually draw one.
Entity Relationship Diagram — Use when asked to model a database's data structure as an entity-relationship diagram (ERD) — entities, attributes, and one-to-one/one-to-many/many-to-many relationships — as the data-modeling counterpart to a class diagram's object-oriented structure (see class-diagram).
Fishbone Diagram — Use when asked about a "fishbone diagram" for root-cause analysis — the same technique as a cause-and-effect diagram (see cause-and-effect-diagram), named for its fish-skeleton shape, also called an Ishikawa diagram (see ishikawa-diagram).
Gantt Chart — Use when asked to build a Gantt chart — a horizontal bar chart showing a project's tasks against a timeline, with dependencies and overlap — for a project with real sequencing between tasks, as distinct from a kanban board (see below), which tracks work status rather than a fixed timeline.
Ishikawa Diagram — Use when asked about an "Ishikawa diagram" for root-cause analysis — the same technique as a cause-and-effect diagram (see cause-and-effect-diagram), named after its creator Kaoru Ishikawa, also called a fishbone diagram (see fishbone-diagram).
Mermaid Diagram — Use when asked to write Mermaid.js diagram syntax — flowcharts, sequence diagrams, Gantt charts, class diagrams, state diagrams, pie charts — a browser-based, Markdown-like alternative to plantuml-diagram, and natively supported inside Markdown on many platforms (GitHub, GitLab, and this environment's own Artifacts).
Object Diagram — Use when asked to model a snapshot of specific object instances and their relationships at one point in time — association, aggregation, composition — as the instance-level counterpart to a class diagram's type-level structure (see class-diagram). See plantuml for the text-based syntax to actually draw one.
Package Diagram — Use when asked to model the high-level organization of a system into packages/modules and their dependencies — as the highest-abstraction structural UML diagram, sitting above class diagrams (see class-diagram) rather than showing individual classes. See plantuml for the text-based syntax to actually draw one.
PlantUML Diagram — Use when asked to write PlantUML diagram source — sequence, class, ERD, activity, state, Gantt, C4, ArchiMate, mind map, WBS, or JSON/YAML visualization diagrams — grounded in joelparkerhenderson/plantuml-examples.
Sequence Diagram — Use when asked to model interactions between objects/components over time as a UML sequence diagram — lifelines, messages, activation bars, combined fragments — as distinct from a use case diagram's user-perspective functionality view (see use-case-diagram). See plantuml for the text-based syntax to actually draw one.
State Diagram — Use when asked to model an object's or system's states and transitions over time — states, events, actions, guards — as distinct from an activity diagram's sequence-of-actions view (see activity-diagram), which models a workflow rather than one object's possible states.
Swimlane Diagram — Use when asked to build a swimlane diagram (also called a cross-functional flowchart) — a process-flow diagram that groups steps into lanes by who or what performs them — as distinct from a plain activity-diagram or flowchart (see below), which shows the sequence of steps without making the responsible party or the handoffs between them explicit.
Timing Diagram — Use when asked to visualize the timing and duration of signals or events over time — horizontal time axis, per-signal lanes — common in digital electronics, communication protocols, and concurrent software behavior, as distinct from a sequence diagram's message-order-without-precise-timing view (see sequence-diagram).
Use Case Diagram — Use when asked to model system functionality from a user's perspective as a UML use case diagram — actors, use cases, association/extend/include relationships — as distinct from a sequence diagram's message-level interaction view (see sequence-diagram). See plantuml for the text-based syntax to actually draw one.
Value Stream Map — Use when asked to build a value stream map — a lean process-analysis diagram tracing material and information flow through a process, distinguishing value-adding steps from waste and quantifying time — as distinct from a plain swimlane-diagram (see below), which shows who does what without that waste analysis.
Wardley Map — Use when asked to build a Wardley map — a strategy map plotting a value chain's components against their evolution from genesis through custom-built and product to commodity — as distinct from a business-model-canvas (see below), which is a static snapshot rather than a map of how components change position over time.

Technology › Systems & safety engineering 3

Causal Analysis Based on System Theory — Use when asked to investigate an incident/accident using CAST (Causal Analysis based on System Theory) — a blame-free, systems-view accident analysis technique built on STAMP/STPA — grounded in joelparkerhenderson/causal-analysis-based-on-system-theory, as distinct from single-root-cause analysis.
Queueing Theory — Use when asked to apply queueing theory to software/business processes — arrival/service rate notation, utilization ratio, Little's Law, or DORA/MTTR metrics derived from queue behavior — grounded in joelparkerhenderson/queueing-theory.
System Quality Attributes — Use when asked to name, define, or choose system quality attributes (SQAs) — non-functional requirements like reliability, scalability, observability, maintainability — for a software system or organizational practice, distinct from functional requirements — grounded in joelparkerhenderson/system-quality-attributes.

Technology › Security & operations 11

Business Continuity Plan — Use when asked to write a business continuity plan (BCP) — an organization-wide plan for keeping critical operations running through a major disruption (facility loss, supplier failure, pandemic, natural disaster) — as distinct from disaster-recovery-testing (see below), which is the IT-systems-only slice of this.
Change Request — Use when asked to write or process a change request — a formal request to modify a specific system, process, or environment under IT/ITIL-style change control — as distinct from [[enterprise-change-management]], which governs organizational and people change (reorgs, new processes, culture shifts) rather than controlled technical or operational changes to a system.
Configuration Management — Use when asked to set up or document configuration management — systematically tracking and controlling a system's settings, versions, and dependencies so its actual state is known and reproducible rather than drifting unrecorded — as distinct from a [[change-request]], which is the approval process for a specific proposed change rather than the ongoing record of a system's current configuration.
Disaster Recovery Plan — Use when asked to write a disaster recovery plan — the written plan for recovering IT systems and data after a major disruption, including recovery objectives, sequence, and backup strategy — as distinct from [[disaster-recovery-testing]] (verifying the plan actually works, rather than the plan itself) and narrower than a [[business-continuity-plan]] (org-wide continuity across people, facilities, and suppliers, not just IT systems and data).
Incident Response Plan — Use when asked to write or review an incident response plan — the pre-defined process for handling a security or operational incident while it's happening, including severity levels, roles, and escalation — as distinct from a [[postmortem]] (the after-the-fact analysis once the incident is over) and a [[business-continuity-plan]] (broader, org-wide continuity planning rather than tactical in-the-moment response).
Keycloak — Use when asked to set up, configure, secure, or troubleshoot Keycloak, the open-source identity and access management server, including realms, clients, users, roles, single sign-on with OpenID Connect or SAML, identity brokering, and deployment. Distinct from [[threat-modeling]], which analyzes risks without configuring an identity provider.
On-Call Rotation — Use when asked to set up or document an on-call rotation — the schedule and process for who's responsible for responding to alerts and incidents outside normal hours, and how that responsibility hands off between people — as distinct from an [[incident-response-plan]], which governs what happens once an incident is declared rather than who's watching for one in the first place.
Postmortem — Use when asked to write or facilitate a postmortem — a blameless, after-the-fact analysis of an incident, its timeline, root cause, and follow-up actions — as distinct from an [[incident-response-plan]] (what happens during the incident, not after) and a routine [[agile-reflection]] (triggered by an incident, not run on a scheduled cadence).
Runbook — Use when asked to write a runbook — a step-by-step operational procedure for a specific, recurring task or system situation, such as restarting a service, rotating a credential, or failing over a database — as distinct from an [[incident-response-plan]], which governs roles and communication during an incident rather than the precise technical steps for one specific action.
Service Catalog — Use when asked to build or document a service catalog — a structured, discoverable list of the IT or business services an organization offers internally or externally, what each includes, and how to request it — as distinct from a [[service-level-agreement]], which defines the performance commitment for one specific service rather than listing what services exist at all.
Threat Modeling — Use when asked to threat model a system or feature — proactively analyzing a design for security weaknesses before it's built — as distinct from penetration-testing (see below), which attacks a system that already exists.

Testing 41

A B Testing — Use when asked to design or automate an A/B test — random traffic allocation, statistical significance, and multivariate testing — as distinct from black/white-box testing technique (see black-box-testing, white-box-testing) or UI/UX evaluation broadly (see ui-ux-testing).
Acceptance Testing — Use when asked to write or run acceptance tests — verifying software meets client/user requirements before release — as distinct from behavior-driven Given/When/Then scenarios (see behavior-driven-development) or lower-level integration/system testing (see integration-testing, system-testing).
Accessibility Testing — Use when asked to test whether a website or application is usable by people with disabilities — WCAG/ADA compliance, automated scanning, and manual/user testing — as distinct from screen-reader-specific verification (see screen-reader-testing) or general usability testing (see usability-testing).
Benchmark Testing — Use when asked to compare a system's performance against a standard or reference point — benchmarking methodology and pitfalls — as distinct from the specific load/stress/performance techniques it often composes (see load-testing, stress-testing, performance-testing).
Black Box Testing — Use when asked to test software from the outside, based only on specifications and inputs/outputs, without knowledge of internal code — equivalence partitioning, boundary value analysis, decision tables — as distinct from white-box testing (see white-box-testing), which requires internal code knowledge.
Boundary Testing — Use when asked to test the edges of an input range or operational limit — minimum/maximum values, off-by-one errors — a specific black-box technique (see black-box-testing) worth its own focus because defects cluster at boundaries.
Capture Playback Testing — Use when asked about record-and-replay test tooling — recording user interactions to generate automated regression tests — as distinct from writing BDD scenarios by hand (see behavior-driven-development), which capture/playback tools can also help automate.
Chaos Testing — Use when asked to deliberately inject failure into a system to test resilience — chaos engineering, fault injection — as distinct from disaster-recovery testing (see disaster-recovery-testing), which validates a specific recovery procedure rather than exploring unknown failure modes.
Command Line Interface Testing — Use when asked to test a CLI tool — command syntax, exit codes, stdout/stderr validation, cross-platform behavior — as distinct from terminal UI testing (see terminal-user-interface-testing), which covers interactive, layout-based terminal applications rather than single-invocation commands.
Compliance Testing — Use when asked to test whether software adheres to regulatory or policy standards (HIPAA, PCI-DSS, GDPR, SOX) — as distinct from security testing broadly (see security-testing), which compliance testing draws on but is scoped specifically to named external requirements.
Database Migration Testing — Use when asked to test moving a database between environments, versions, or platforms — data integrity validation, rollback testing — as distinct from testing schema changes specifically (see database-schema-migration-testing), which is a narrower, structure-focused case.
Database Schema Migration Testing — Use when asked to test a database schema change (adding a column, renaming a table, altering a constraint) — forward-migration correctness, rollback/reversibility, and data-integrity preservation — as distinct from broader environment-to-environment database migration (see database-migration-testing).
Decision Record Testing — Use when asked to verify that a codebase actually reflects a recorded architectural decision (an ADR/DR) — reviewing a decision record for testability, or checking code/CI for drift from a decision already made — as distinct from writing the decision record itself (see architecture-decision-record, decision-records).
Disaster Recovery Testing — Use when asked to test backup restoration, failover, and business-continuity recovery procedures — recovery time/point objectives (RTO/RPO) — as distinct from chaos testing (see chaos-testing), which explores unknown failure modes broadly rather than validating one defined recovery plan.
End to End Testing — Use when asked to test a full application flow from a real user's perspective — as distinct from unit testing (see unit-testing) or integration testing (see integration-testing), which end-to-end testing sits above, exercising the whole system together rather than isolated units or component pairs.
Failover Testing — Use when asked to test automatic switchover to a backup component, server, or network on primary failure — as a specific slice of chaos testing (see chaos-testing) and disaster recovery testing (see disaster-recovery-testing) focused specifically on redundancy activation.
Field Testing — Use when asked about testing software in real-world production environments rather than controlled lab conditions — real hardware, real networks, real usage patterns — as distinct from the controlled, staged environments most other testing types (unit, integration, system) run in.
Fitness Function Testing — Use when asked to write an architectural fitness function — an automated, ongoing check that a codebase's structure keeps meeting a specific architectural characteristic (dependency direction, cyclomatic complexity, coupling) — as distinct from a one-off architecture review or a functional/unit test verifying business behavior.
Functional Testing — Use when asked to verify that an application's features work as specified — as the general discipline underlying more specific techniques (black-box testing, acceptance testing, UI automation) — as distinct from non-functional testing of quality attributes like performance or security (see performance-testing, security-testing).
Fuzz Testing — Use when asked to fuzz an application — feeding invalid, unexpected, or random inputs to discover crashes and security vulnerabilities — coverage-guided, grammar-based, and mutation-based fuzzing, as distinct from boundary testing's targeted edge-value approach (see boundary-testing).
Integration Testing — Use when asked to test the interaction between modules/components — big-bang, top-down, bottom-up, or hybrid integration strategies — as the layer between unit testing (see unit-testing) and system/end-to-end testing (see system-testing, end-to-end-testing).
Load Testing — Use when asked to test how an application performs under expected and peak user load — capacity limits, breaking points — as distinct from stress testing beyond normal capacity (see stress-testing) or sudden-spike testing (see peak-testing), which load testing's staged progression leads into.
Localization Testing — Use when asked to test whether software has been correctly adapted for a specific language/region — UI layout with translated text, locale-specific formats, cultural appropriateness, legal compliance — as the verification counterpart to internationalization implementation (see locale).
Monte Carlo Testing — Use when asked to test a system using randomly-sampled inputs drawn from defined probability distributions to estimate reliability statistically — as distinct from fuzz testing (see fuzz-testing), which searches for specific crashing inputs rather than estimating overall statistical reliability.
Mutation Testing — Use when asked to measure whether a test suite can actually detect faults — mutation score, killed vs. surviving mutants — as a more rigorous alternative to code coverage percentage, and a companion to test-driven development (see test-driven-development).
Peak Testing — Use when asked to test system behavior during predictable high-traffic periods (peak business hours, seasonal spikes) — as distinct from stress testing beyond normal capacity generally (see stress-testing) or sudden unpredictable spikes specifically, which peak testing's predictable-timing focus differs from.
Penetration Testing — Use when asked to simulate an attack on a system to find security vulnerabilities — reconnaissance, scanning, exploitation, reporting — black-box vs. white-box approaches, as one specific security-testing technique among others (see security-testing). Requires proper authorization — never simulate an attack against a system without explicit permission.
Performance Testing — Use when asked to measure application responsiveness and resource use under workload — the umbrella covering load, stress, endurance, and spike testing (see load-testing, stress-testing) — to identify bottlenecks and confirm the system meets performance requirements.
Regression Testing — Use when asked to verify that a change hasn't broken existing functionality — test-case selection, defect reporting/resolution, retesting — the discipline that makes safe, frequent releases possible, closely tied to test-driven development's refactor-safety guarantee (see test-driven-development).
Screen Reader Testing — Use when asked to test a website/application with an actual screen reader (JAWS, NVDA, VoiceOver) — element announcement, keyboard navigation, multimedia accessibility — as the most specific verification layer within accessibility testing broadly (see accessibility-testing).
Security Testing — Use when asked to evaluate a system's security — vulnerability scanning, authentication/authorization testing, encryption verification, security configuration review — the umbrella discipline penetration testing (see penetration-testing) and compliance testing (see compliance-testing) both sit within.
Shift Left Testing — Use when asked to move testing earlier in the development lifecycle — code review, static analysis, and testing-as-you-write rather than testing-after-the-fact — the strategic principle underlying test-driven development (see test-driven-development) and CI-integrated quality gates broadly.
Split Testing — Use when asked to compare two or more variations of a design/interface to see which performs better — the general step-by-step process (goal, variation, random allocation, data collection, analysis) shared with A/B testing (see a-b-testing), applied to UI/UX design decisions specifically.
Stress Testing — Use when asked to test a system under extreme conditions beyond its normal capacity — finding the breaking point and recovery behavior — as one specific variant within performance testing broadly (see performance-testing), distinct from load testing at expected capacity (see load-testing).
System Testing — Use when asked to evaluate an entire integrated system as a whole — combining functional, performance, security, usability, compatibility, and regression checks — as the whole-system layer between integration testing (see integration-testing) and acceptance testing (see acceptance-testing).
Terminal User Interface Testing — Use when asked to test an interactive, screen-drawing terminal application (ncurses-style, with grid/row/column layout) — simulated keystrokes, screen-scraping, escape-sequence handling — as distinct from single-invocation CLI testing (see command-line-interface-testing).
UI UX Testing — Use when asked to evaluate a user interface's usability and user satisfaction — user testing, split testing, surveys, heatmaps, eye-tracking, expert review — as a set of techniques distinct from, but overlapping with, usability testing specifically (see usability-testing) and user-centred design methodology broadly (see user-centred-design).
Unit Testing — Use when asked to write a unit test — isolating the smallest testable part of an application (a function, method, class) and verifying it independently — the foundational layer below integration testing (see integration-testing) and the layer test-driven development operates at (see test-driven-development).
Usability Testing — Use when asked to run a usability test — observing real users attempting real tasks to find friction points — the core user-research method within UI/UX testing (see ui-ux-testing) and user-centred design (see user-centred-design).
Visual Testing — Use when asked to catch unintended UI appearance changes — screenshot-baseline comparison, pixel/DOM/AI-based diffing — as distinct from functional testing (see functional-testing), which validates behavior rather than appearance, and complementary to it.
White Box Testing — Use when asked to test software using knowledge of its internal code — statement/branch/path coverage, static and dynamic analysis — as distinct from black-box testing (see black-box-testing), which tests only inputs/outputs without code knowledge.