Results for “composability”

Create, update, or migrate Wear OS projects using Compose Material3, Foundation, and Navigation3 libraries with official component samples and migration guidance.

Composition Patterns

Use to build Science's data, code, and materials availability — mandatory deposition in approved repositories, accession numbers, a compliant data-availability statement, and materials/reagent sharing.

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

Provides React composition patterns to avoid boolean prop proliferation, build flexible component libraries, and design reusable APIs, including React 19 changes.

Adapt Android app UIs to phones, tablets, foldables, desktops, and other devices using Compose, including window size handling, multi-pane layouts, and adaptive navigation.

Expert guidance for working with Wear OS Compose Material3. Use this skill when creating, updating or migrating Wear OS projects. This includes the androidx.wear.compose.material3, androidx.wear.compose.foundation and androidx.wear.compose.navigation3 libraries. Also working with core components such as AppScaffold, ScreenScaffold and TransformingLazyColumn. Migration from earlier versions such as Material 2.5 and Horologist.

Harness Compound

Use to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.

Analyze the spatial and structural qualities of a screen design, evaluating balance, whitespace, rhythm, and gestalt principles to identify compositional weaknesses and propose specific fixes.

Build AI agents and apps with Composio - access 200+ external tools with Tool Router or direct execution

Provides React composition patterns to avoid boolean prop proliferation, covering compound components, state management, and React 19 API changes.

Generate traceability matrix and quality gate decision. Use when the user says "lets create traceability matrix" or "I want to analyze test coverage"

Reviews cohesion, naming, responsibility, complexity, and maintainability. Do not use as a default companion to every code change.

Analyzes .NET test suites for duplicated boilerplate, copy-paste tests, and structural maintainability issues, producing a report with concrete before/after refactoring suggestions.

Universal transformation λ(ο,K).τ with recursive self-improvement. USE WHEN routing reasoning, validating knowledge graphs, preparing CICM/ANZCA examinations, or when self-improvement of reasoning/architecture/context is required. Routes queries through R0-R3 complexity pipelines, validates topology (η≥target) and governance (KROG), emits per style (Φ), and compounds learnings into knowledge K. Triggers on complexity assessment, multi-step reasoning, examination mode, or /λ invocation.

Establish clear naming conventions for design assets, components, and tokens to make design systems predictable and maintainable.

Builds reusable Convex components with isolated tables and app-facing APIs for new components, reusable backend modules, integrations, or component boundary work.

Imported skill utils from langchain

Architects, reviews, and scales backend systems with structured blueprints, trade-off analysis, and audit reports.

Build reproducible ML experiment plans with hypotheses, metrics, and ablations. Use when: (1) planning experiments, (2) comparing variants, (3) defining acceptance thresholds. NOT for: long-running experiment execution.

CAP Theorem

Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.