Results for “standards”

Update existing Lattice standards after a significant change — the update-mode counterpart to lattice-init. Scans .lattice/standards/, asks what changed, and routes each affected standard to its refiner's revise mode, recording a git-native change note. Use when the user says 'update refiners', 'refiners update', 'our standards changed', 'update our standards', 'the architecture changed, update the standards', 'we switched languages, update the standards', 'revise standards after a big change', or 're-run the refiners'.

The English summary is being prepared. Showing the original description.

Audit and strengthen security for applications running on GKE. Configure pod traffic restrictions, sandbox isolation, namespace security standards, and Secret Manager volume mounts to protect workloads at the application and namespace level.

• Auditing GKE security settings
• Restricting communication within a namespace
• Isolating risky pods and applying security standards

Apply Apache ShardingSphere’s written coding standards during implementation or review, covering naming, Java constructs, tests, and Maven dependencies. Also audit a specified scope without editing files, combining automated checks with manual inspection of applicable rules.

• Check changed code against written repository standards
• Review Java naming and declaration conventions
• Verify changed Maven dependency declarations

Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution, customising its embedded defaults for the team's product process. Use when setting up a new project, defining product standards, or when the user says 'set up requirement standards', 'define feature standards', 'configure requirement forge', 'define how features should be structured', or 'requirement forge refiner'.

The English summary is being prepared. Showing the original description.

Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.

• Reviewing changes on a branch or pull request
• Checking changes since a chosen commit or tag
• Checking compliance with documented coding standards

Define project quality standards in CONSTRAINTS.md, connect measurable targets to checks, and inspect changes for weakened safeguards. It helps teams choose thresholds and catch skipped tests, suppressed warnings, unfinished code, or lowered standards during agent development.

• Set quality standards before starting agent development
• Choose coverage and performance thresholds
• Detect skipped tests and suppressed warnings

Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.

• Review a branch or pull request
• Check changes since a specific commit
• Find missing requirements or unintended scope

Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.

The English summary is being prepared. Showing the original description.

Signpost (not a knowledge pack) for the ECSS European space standards: the E-ST-10 system engineering family, the discipline standards a reader commonly mis-cites (radiation is E-ST-10-12, not a RAM standard; software is E-ST-40, not E-ST-70), the M-branch project management standards, the Q-branch product assurance standards, and the sustainability and system documents, with designation, edition, owner, status, and catalogue URL only. Contains no source content. Free process paths are existing NASA packs in this catalogue, named by slug, and are not ECSS clause substitutes. Several needs have no in-repo pack.

The English summary is being prepared. Showing the original description.

Set consistent Python conventions for naming, formatting, type checking, and documentation. Configure ruff and mypy or pyright, write clear function descriptions, and organize README and changelog content so a team can maintain shared standards.

• Set up Python linting and formatting
• Define shared team coding conventions
• Review type hints and function documentation

Guides Kubernetes security configuration with network restrictions, Pod execution rules, and role-based access control. Use its configuration examples to separate workloads, limit permissions, and enforce deployment requirements across a cluster.

• Restricting communication between application components
• Giving ServiceAccounts only the permissions they need
• Running Pods with restricted privileges

Design and review REST and GraphQL APIs with consistent naming, data structures, error responses, pagination for large result sets, and versioning strategies. Helps teams define shared standards and plan changes that existing clients can adopt gradually.

• Designing a new REST or GraphQL API
• Reviewing API specifications before implementation
• Establishing shared API design standards

Build NFT contracts using ERC-721 and ERC-1155, standards for unique assets and multiple token types. Covers issuance limits, descriptive metadata, marketplace integration, and royalty information for art collections, collectibles, and game items.

• Creating NFT art and collectible collections
• Managing multiple game item types
• Designing metadata storage and references

Consolidated Responsible AI standards reference: NIST AI RMF 1.0, AI STRIDE threat-modeling overlay, EU AI Act risk tiers, and an open-standards catalog with phase mapping

The English summary is being prepared. Showing the original description.

Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card, CTA, layout, review the UI, fix the design, design system, design tokens, spacing, typography scale, button standards, mobile design. Also triggers for any production design decision where contrast, accessibility, spacing, or visual hierarchy matters.

The English summary is being prepared. Showing the original description.

Expert CSRD (Corporate Sustainability Reporting Directive, EU 2022/2464) compliance advisor. Use this skill whenever a user asks about CSRD, European Sustainability Reporting Standards (ESRS), double materiality assessment, sustainability reporting obligations, ESG disclosure, CSRD scope and thresholds, value chain reporting, XBRL digital tagging, third-party assurance, CSRD gap assessments, CSRD implementation timelines, ESRS E1–E5 environmental standards, ESRS S1–S4 social standards, ESRS G1 governance, the 2026 Omnibus scope change (Directive (EU) 2026/470, 1,000+ employees) and revised/simplified ESRS (July 2026), CSRD vs GRI/TCFD/SASB alignment, or any EU corporate sustainability reporting question. Trigger even if the user only mentions "ESG reporting Europe", "sustainability disclosure EU", or "non-financial reporting".

The English summary is being prepared. Showing the original description.

Expert CSRD (Corporate Sustainability Reporting Directive, EU 2022/2464) compliance advisor. Use this skill whenever a user asks about CSRD, European Sustainability Reporting Standards (ESRS), double materiality assessment, sustainability reporting obligations, ESG disclosure, CSRD scope and thresholds, value chain reporting, XBRL digital tagging, third-party assurance, CSRD gap assessments, CSRD implementation timelines, ESRS E1–E5 environmental standards, ESRS S1–S4 social standards, ESRS G1 governance, CSRD vs GRI/TCFD/SASB alignment, or any EU corporate sustainability reporting question. Trigger even if the user only mentions "ESG reporting Europe", "sustainability disclosure EU", or "non-financial reporting".

The English summary is being prepared. Showing the original description.

Check data compliance with construction standards. Validate data against ISO 19650, IFC, COBie, UniFormat standards.

The English summary is being prepared. Showing the original description.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

The English summary is being prepared. Showing the original description.

Facilitate a structured conversation to define clean code principles for a repository. Produces a formal clean-code.md document that the clean-code atom will use as its override. Use when setting up coding standards, defining code quality rules, or when the user says 'setup clean code', 'define coding standards', 'code quality principles', 'coding guidelines', or 'help me define my code standards'.

The English summary is being prepared. Showing the original description.

The art of reviewing code that improves both the codebase and the developer - sharing knowledge, maintaining standards, and building cultureUse when "code review, PR review, pull request, merge request, review comments, LGTM, review feedback, approve PR, request changes, review checklist, code quality, review standards, code-review, pull-request, PR, quality, standards, feedback, collaboration, mentoring" mentioned.

The English summary is being prepared. Showing the original description.

Use when writing or refactoring modern C# with maintainability and performance standards. Keywords: coding standards, C# best practices, refactor C#, records, pattern matching, async best practices.

The English summary is being prepared. Showing the original description.

Signpost (not a knowledge pack) for the systems-engineering standards landscape — ISO/IEC/IEEE 15288, 24748, 29148, 42010, 15026, 24765; INCOSE SE Handbook & Vision 2035; OMG SysML; SAE/EIA 1001/649/748; ECSS space standards; NATO AAP-48; CMMI; NIST SP 800-160; and more. Contains NO source content: it lists each standard's designation, title, purpose, owning SDO, whether it's redistributable, and where to get it. Use when you need to identify or locate an SE standard — most are paywalled/all-rights-reserved and cannot be packaged, so this points you to the owner (and to the open packs where one exists).

The English summary is being prepared. Showing the original description.

Knowledge base from the OUSD(R&E) guidebook Implementing a MOSA in DoD Programs (Feb 2025). Use for the Modular Open Systems Approach as a DoD acquisition + design discipline: the statutory/regulatory basis (10 U.S.C. 4401–4403, FY2017/FY2021 NDAA, DFARS), the five OUSD(R&E) pillars, the plan→modularize→identify→define→standardize interface lifecycle, technical levers (WBS/MIL-STD-881F taxonomy, standards profiling, API-first software, COTS/cybersecurity), MOSA assessment metrics and tools (PART/OAAT/KOSS/SEAM/MAUT), technology-change and DMSMS management, roadmaps, MOSA across the six AAF pathways, and contracting/IP/data-rights mechanics. SCOPE LIMITS: this is U.S. DoD weapon-system acquisition policy, not a general open-architecture or interface-standards reference — it names standards (FACE, OMS, DISR) without reproducing them, is light on detailed engineering of any specific standard, and does not cover the underlying SE processes (use dau-se-guidebook / nasa-npr-7123) or general systems-engineering theory (use sebok).

The English summary is being prepared. Showing the original description.