Results for “software-defined-perimeter”

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language, with scoring and diagnostic tools for evaluating domain model quality.

Generates a high-level technical architecture specification for an epic from a Product Requirements Document, including system diagrams, component lists, and estimates.

Creates detailed technical implementation plans for features based on a Feature PRD, including system architecture, database schema, API design, and frontend component hierarchy.

Design and implement clear, modular, resilient software and create executor-grade implementation plans with explicit scope, drift checks, verification gates, tests, STOP conditions, dependencies, and delegated-work review. Use for development, refactoring, architecture, implementation planning, safe migrations, handoffs to another engineer or agent, or verifying delegated code changes.

Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.

STRIDE Threat Model

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", or "strategic design". Also trigger when splitting a monolith into services, defining microservice boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.

Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.

Computes the SQuAD metric using torchmetrics, given predictions and ground truth. Use when evaluating question-answering outputs with exact match and F1 scores.

Proposes exactly one personal side-project idea per invocation, sized to a 1-3 day MVP. Targets CLI, automation, LLM, DX, productivity, and data-viz angles; avoids clichés like TODO apps, weather apps, and pomodoro timers. Output is an 8-section brief including a ready-to-paste coding-agent prompt. Use for morning/daily idea rituals and weekend-hack ideation. Don't use for existing-product feature proposals (Spark), dialogue brainstorming (Riff), or prototype implementation (Forge).