「architecture」の検索結果

Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.

日本語の概要は準備中です。原文の説明を表示しています。

AWS development with infrastructure automation and cloud architecture patterns

日本語の概要は準備中です。原文の説明を表示しています。

Master software architect specializing in modern architecture

日本語の概要は準備中です。原文の説明を表示しています。

Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.

日本語の概要は準備中です。原文の説明を表示しています。

Production-grade Android app development guide covering native (Kotlin/Java), cross-platform (Flutter, RN, KMM), and hybrid architectures.

日本語の概要は準備中です。原文の説明を表示しています。

AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.

日本語の概要は準備中です。原文の説明を表示しています。

A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

日本語の概要は準備中です。原文の説明を表示しています。

Interactive Flutter Widget implementation assistant that guides you through widget implementation decisions by asking structured questions about state management, widget type (screen/component), and state sharing. Use this skill when you need help determining the appropriate Flutter widget architecture for your implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Single Source of Truth (SSOT) guidelines for SwiftUI state management. Use when designing state architecture, choosing between @State/@Binding/@StateObject/@ObservedObject/@EnvironmentObject, fixing state synchronization issues, refactoring duplicated state, or reviewing state management in PRs. Covers SSOT principles, property wrapper selection, state lifting, and common violations.

日本語の概要は準備中です。原文の説明を表示しています。

Androidプロジェクトのアーキテクチャ設計を支援。プロジェクト特性に応じてMVI/MVVM/シンプルComposeから最適なパターンを提案し、パッケージ構造の設計と既存プロジェクトの分析を行う。

Magazine-grade, collage-driven editorial system: warm paper canvas, surreal plaster-and-architecture imagery, oversized display type, hairline rules, and Roman-numeral section markers.

日本語の概要は準備中です。原文の説明を表示しています。

Raw, anti-design aesthetic inspired by concrete architecture with unadorned elements, jarring layouts, and functional minimalism.

日本語の概要は準備中です。原文の説明を表示しています。

Create or revise the SDD Composy technical specification (tasks/prd-SLUG/techspec.md) from the approved PRD, resolved stories, and mapped codebase, with DEC/RISK and TU/TI/E2E traceability and a human gate. Use when the product contracts are approved and architecture is needed — 'criar a spec técnica', 'techspec do prd-SLUG', 'design the solution for…'. Do NOT use to change product scope, before PRD and stories approval, or for design notes outside SDD.

日本語の概要は準備中です。原文の説明を表示しています。

Deliver a small bounded change inside an initialized SDD Composy workspace through the quick path: at most five implementation files, a registered TASK, TDD, evidence, trace, and a verified verdict, escalating otherwise. Use for a precise objective with no existing task — 'ajuste rápido via SDD', 'quick fix under SDD', 'small change to X in the SDD flow'. Do NOT use for an already registered task (sdd-execute), for architecture, migrations, or destructive work, or in repositories without SDD Composy (other plugins' quick).

日本語の概要は準備中です。原文の説明を表示しています。

Produce a deterministic, read-only evidence map of the repository for SDD Composy (languages, manifests, commands, modules, boundaries, staleness) and publish the context bundle only on request. Use before a PRD or TechSpec, or when the map is stale — 'mapear o repositório', 'atualizar o contexto do código', 'what does this codebase look like for SDD'. Do NOT use for architecture decisions, code review, or repository exploration without an SDD workspace.

日本語の概要は準備中です。原文の説明を表示しています。

Design an approval-gated feature specification from approved requirements. Use when PWDEV Flow discovery is complete and the user needs architecture decisions, component boundaries, quality constraints, and a definition of done.

日本語の概要は準備中です。原文の説明を表示しています。

Write and refine high-quality user stories — INVEST criteria, "As a X, I want Y, so that Z" format, Gherkin acceptance criteria when applicable, definition of ready, anti-patterns, and a review checklist. Use when creating or reviewing user stories, PRD section 6, backlog items, or acceptance criteria. Do NOT use for technical specs, architecture decisions, or task decomposition.

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate ideation, explore alternatives, and refine concepts through structured brainstorming techniques before implementation. Use when starting new projects, designing features, exploring solutions, evaluating tradeoffs, challenging assumptions, generating creative ideas, planning architecture, or refining rough concepts into detailed designs.

日本語の概要は準備中です。原文の説明を表示しています。

Build modern Next.js 13+ applications using App Router architecture with Server Components, Client Components, and advanced routing patterns. Use when implementing server-first rendering, creating nested layouts, building parallel routes, implementing intercepting routes, using React Server Components, optimizing data fetching with server-side async components, implementing streaming with Suspense, managing client-side interactivity boundaries, or leveraging Next.js 13+ app directory features for performant, SEO-friendly React applications.

日本語の概要は準備中です。原文の説明を表示しています。

Build reusable, composable, and maintainable React/Vue/Angular components following established design patterns like compound components, render props, custom hooks, and HOCs. Use when creating component libraries, implementing component composition, building reusable UI elements, designing prop APIs, managing component state patterns, implementing controlled vs uncontrolled components, creating compound components, using render props or children as functions, building custom hooks, or establishing component architecture standards.

日本語の概要は準備中です。原文の説明を表示しています。

Build efficient React applications using Next.js Server Components that render on the server, reducing client bundle size, improving performance, and enabling direct database access. Use when fetching data server-side, reducing JavaScript bundle size, accessing databases directly in components, implementing streaming with Suspense, creating layouts that only render once, optimizing Core Web Vitals, or building SEO-friendly applications with server-first architecture.

日本語の概要は準備中です。原文の説明を表示しています。

Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.

日本語の概要は準備中です。原文の説明を表示しています。

Refresh drift-prone documentation against current code. Reads docs/architecture/freshness-catalog.yml, diffs against the last sweep's upstream/main anchor, regenerates mechanical entries, processes editorial markers, and opens one PR per sweep with a report file.

日本語の概要は準備中です。原文の説明を表示しています。

Introduce the cross-section read interface boundary (I<Section>ServiceRead) for one section's service per memory/architecture/section-read-write-split.md. Audits the surface, evaluates which methods belong on the read interface, sets up the workspace, dispatches a subagent that introduces the interface and migrates non-section callers, opens a PR. Use when the user says 'read split for X', 'split <Section>Service', 'add I<Section>ServiceRead boundary', 'apply the section-read-write-split rule to <Section>', or any variation of carving the cross-section read surface out of a section's full service interface. Reference implementation is Teams (PR 678). Operates on one section per invocation.

日本語の概要は準備中です。原文の説明を表示しています。