Results for “system”

Use when tuning the numbers in a game — economy curves, progression rates, difficulty pacing, drop tables, win/loss odds, time-to-X targets, and currency velocities. Triggers on "balance pass", "tune the economy", "progression curve", "difficulty curve", "drop rate", "XP curve", "TTK", "time-to-content", "balance the economy", "spreadsheet model", "economy sim", or a system spec from game-systems-designer with `TBD` placeholders. Produces an economy spreadsheet, balance pass plan, sim outputs, and per-system balance tables. Stops at the numbers — does not change system rules or pricing. For systems design see game-systems-designer; for store catalog see iap-manager.

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

Use when designing the systems of a game from a locked concept — core loops, meta loops, player verbs, progression, content systems, level structure, and narrative integration. Triggers on "game design doc", "GDD", "system spec", "core loop design", "progression design", "level design", "MDA", or "design the systems". Produces a design doc plus per-system specs that game-balancer numbers, iap-manager stocks, and godot-engineer builds. Stops at design — no number tuning, pricing, or engine code. For balance numbers see game-balancer; for the engine implementation see godot-engineer.

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

Knowledge base from the NASA Systems Modeling Handbook for Systems Engineering (NASA-HDBK-1009A Rev A, 2025). Use for model-based systems engineering (MBSE) wired into NASA's NPR 7123.1 SE processes: the three aspects of MBSE (language / methodology / framework), the NASA SE Engine and its two OOSEM-derived steps (Model Planning, Setting Up the Model), the Modeling Plan as a SEMP subset, the tool-agnostic NASA SE metamodel of elements and relationships across the four SysML pillars (structure / behavior / requirements / parametrics), worked SysML diagrams and tables for stakeholders, requirements, structure and V&V, generating SE work products (ConOps, MOE, MOP, TPM, V&V), the MBSE Grid framework, alternative modeling approaches (PBR, Scenario, System Specification, Verification), and the ConOps model-content template. Scope is bounded to four common technical processes (Stakeholder Expectation Definition, Technical Requirements Definition, Product Verification, Product Validation). Does NOT teach SysML itself, mandate a tool, define NPR 7123.1 processes, cover technical-management processes 10-17, or reproduce the OMG SysML specification.

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

Knowledge base from the FAA Systems Engineering Manual (SEM) v1.0.1. Use for civil-agency systems engineering as the FAA practices it inside the Acquisition Management System (AMS) and the National Airspace System (NAS): the five-phase AMS lifecycle and its decision points; operational concept development and implementation-free functional analysis (ConOps, FFBD/N², CMLs); requirements analysis and architectural design synthesis (PRS→MRS, the PRD ratchet pPRD→iPRD→fPRD, RAM, ISEF/DoDAF views, CPRs); the seven technical management disciplines (Integrated Technical Management/SEMP, Interface Management/IRD-ICD, Risk-Issue-Opportunity, Configuration Management, SE Information Management, Decision Analysis, Verification & Validation); and the specialty disciplines (RMA via Service Threads/STLSC, Life Cycle Engineering, E3/Spectrum, Human Factors, Information Security via the NIST RMF, System Safety via the SMS, and Hazardous Materials/Environmental/EOSH). Scope limits: this is FAA-specific guidance, not policy — it is a tailorable menu that points outward to companion handbooks (FAA-HDBK-006A for RMA, the SMS Manual, the NIST 800-series) rather than restating generic SE theory; it is thin on detailed cost estimating, contracting/FAR law, software-development methodology, named anti-pattern catalogues, and any non-FAA or non-civil-aviation lifecycle. Source has no page numbers in the extracted text (~360 pp.).

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

Master orchestrator for the 5-step productivity system. Runs the full audit-architect-analyst-refinery-compounder loop or individual steps. Use when: (1) "run the full loop", "start the system", "architect system", (2) "run step N", "run audit", "run architect", (3) "what step am I on?", "system status", "where am I in the loop?", (4) "continue", "resume", "next step". Manages state, sequencing, and skill chaining across all 5 steps.

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

Evaluate substantial software changes against the actual problem, current system, and concrete users or components that need them. Choose a sufficient scope, assess consequences, and, when implementation is requested, make the change and verify its behavior.

• Assessing whether a feature proposal is needed
• Reducing the scope of a refactor or migration
• Checking who needs a proposed API or data field

Plan system architecture by comparing technical options, component relationships, and requirements such as performance, security, and growth. Produce architecture diagrams, data flow diagrams, decision records, and technology comparisons that explain the reasoning behind a proposed design.

• Planning the architecture of a new system
• Comparing technology options and trade-offs
• Documenting component relationships and data flows

Build a design system from product code, Figma designs, and brand materials. Organize colors, typography, assets, and writing guidelines, then create reusable React components and interactive screen examples that follow the source designs.

• Organize brand assets and design guidelines
• Create reusable React components from existing designs
• Recreate product screens as an interactive UI kit

Develop a research question, search and verify literature, and combine findings into an academic report. Modes also support guided research discussions, claim checking, paper comparisons, and systematic reviews with optional meta-analysis, which statistically combines study results.

• Clarify a research direction through guided questions
• Search literature and compare findings across sources
• Check specific claims against supporting sources

Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.

• Creating an onboarding guide for a codebase
• Mapping system architecture and dependencies
• Planning a legacy system migration or rewrite

Write and edit system prompts, tool instructions, and agent definitions with clear structure and explicit rule strength. It guides tag use, placement of critical constraints, concise wording, and practical examples that show how tools should be used.

• Drafting system prompts for agents
• Clarifying required and optional instructions
• Writing tool explanations with runnable examples

Investigate suspected rootkits, malware that hides its presence, by comparing process lists, inspecting memory, and checking system integrity. Use Volatility and Windows or Linux scanners to identify hidden processes, suspicious drivers, altered system calls, and concealed connections.

• Investigating compromise when standard tools show no anomalies
• Comparing process lists to find hidden activity
• Examining suspicious drivers and concealed connections

Inspect Linux scheduled tasks, services, shell profiles, shared library settings, and SSH keys for mechanisms that maintain attacker access. Correlate findings with audit logs to produce a timeline, risk scores, and remediation commands.

• Investigating how attackers maintained access to a Linux host
• Hunting for suspicious scheduled tasks and services
• Building a timeline from persistence-related audit events

Prepare for CMMC Level 2, a cybersecurity certification for defense contractors. Define the systems handling controlled information, review security requirements, calculate the SPRS assessment score, and organize remediation plans and evidence into a readiness report.

• Define the assessment scope for systems handling controlled information
• Calculate an SPRS score and prioritize unmet security requirements
• Prepare security plans, remediation milestones, and assessment evidence

Build AI workflows with DSPy by defining inputs and outputs and combining reusable components. Create question answering systems that use retrieved documents, tool-using agents, and automatically optimized prompts, then compare results with evaluation data.

• Build question answering systems that use retrieved documents
• Optimize prompts using examples and evaluation metrics
• Combine AI tasks into reusable processing stages

Organize EU AI Act compliance work with references to Articles and Annexes. Classify AI systems by risk, plan conformity assessments that check regulatory requirements, prepare technical documentation checklists, and map obligations and deadlines to organizational roles.

• Reviewing risk classification for a new AI system
• Planning conformity assessments for high-risk AI
• Preparing technical documentation checklists

Convert long Markdown specifications, reports, and plans into a single HTML document with a sticky table of contents, search, section tracking, and code-copy buttons. Apply previously configured brand colors and layout styles.

• Turn long specifications into navigable HTML documents
• Add search and a table of contents to reports
• Apply consistent brand styling to technical documents

Review an AI system's EU AI Act readiness through six structured questions. Produce an article-cited assessment covering risk classification, conformity checks, organizational obligations, transparency, and general-purpose models, with gaps and three prioritized actions.

• Reviewing a new or materially changed AI system
• Checking readiness before an EU launch
• Refreshing an annual compliance assessment

Build or update Figma screens from code or descriptions using an existing design system, a shared set of components and visual rules. Assemble sections with reusable components, colors, spacing, and styles, then check their appearance.

• Recreate an application page in Figma
• Build a landing page with shared components
• Update a Figma screen to match code

Write a game design document for one system, such as combat, crafting, or dialogue. Work through sections with specialist agent input, check dependencies against existing designs, and save approved sections with progress records for later continuation.

• Writing a combat or crafting system design
• Checking dependencies against existing game designs
• Developing specifications with specialist agent input

Investigate recurring problems by mapping feedback loops, the cycles through which effects influence their causes. Identify underlying structures, match known patterns, and assess where changes could help and what unintended effects they might produce.

• Investigating recurring incidents
• Understanding coordination problems as teams grow
• Assessing unintended effects before changing a policy

Helps manage and troubleshoot Linux, macOS, and Windows systems. Guides checks of CPU, memory, disks, networks, and logs, then supports service configuration and security hardening with explanations suited to the operating system.

• Investigating slow systems and resource usage
• Finding causes of low disk space
• Checking failed services and their logs

Build AI workflows with DSPy by defining inputs and outputs and combining reusable components. Create question answering systems that use retrieved documents, tool-using agents, and automatically optimized prompts, then compare results with evaluation data.

• Build question answering systems that use retrieved documents
• Optimize prompts using examples and evaluation metrics
• Combine AI tasks into reusable processing stages

Create and update shared design rules in Stitch, including colors, fonts, and corner shapes, then apply them to existing screens. Keep a DESIGN.md file and project metadata alongside the design system.

• Apply shared design rules across existing screens
• Turn a theme description into concrete design values
• Create or update a design system in Stitch