Results for “attribute-collection”

Search reference implementations and code examples from Adobe's Block Collection and community Block Party for AEM Edge Delivery blocks, plugins, and build tools.

Guides developers through capturing diagnostic artifacts to diagnose production .NET performance issues, including tool selection and data collection across Windows, Linux, containers, and Kubernetes.

Extract structured resources (icons, metadata, text, forms, videos, social links) from any webpage using playwright-cli.

Provides guidelines and best practices for aggregates and aggregate roots, referencing detailed documentation.

Qdrant API skill. Use when working with Qdrant for collections, root, telemetry. Covers 73 endpoints.

Discovers the core attributes of the current code repository and its projects — languages, frameworks, tooling, and where things live — and writes a concise reference section directly into the project's AGENTS.md or CLAUDE.md for other skills, agents, and hooks to consume. Use when scanning, analyzing, or detecting the project's technology stack, build tools, or repository structure. Does not create or update project documentation — use project-documentation for writing feature or system docs.

TRAK: Attributing Model Behavior at Scale

Extract GitHub repository details and contributor contact information using keywords, star counts, and update dates via the BrowserAct API.

Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction design across any domain (portfolios, e-commerce, SaaS, adult content, technical showcases). This skill should be used when users need exhaustive design research, pattern recognition across large example sets, or systematic visual analysis for competitive positioning.

Researches authoritative APIs and data sources for a project, producing per-API docs, a data catalog, and an integration blueprint for a React + Supabase + Vercel + AI stack.

Extracts Amazon product details, buy box owner, other sellers' prices, and seller ratings for a given ASIN using the BrowserAct API.

Garbage collection for your Claude Code configuration. Periodically scans ~/.claude (skills, memory, hooks, permissions, MCP servers, caches) for redundant, stale, orphaned, or low-value items, then walks the user through a confirm-each-deletion cleanup. Use when the user says "clean up my config", "config GC", "too many skills", "audit my setup", "my .claude is bloated", or asks for a periodic config review.

Almost every object-storage mistake comes from carrying filesystem instincts into

Memory (aaaf-memory)

Extracts structured product data from Amazon search results, including prices, ratings, sales estimates, and shipping info, using the BrowserAct API.

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.

Aggregate cross-asset quality control for campaigns. Use when the user requests 'run QC', 'quality check campaign', 'review all assets', or 'generate QA report'.

Analyzes a class for primitive obsession and proposes value object extractions with validation, structure, and refactoring guidance.

Audits image usage across a project by comparing required image slots against available files, reporting matches, mismatches, missing assets, and broken references.

Coordinates multi-service releases, manages container registries, and sets up CI/CD pipelines across platforms.

Archive merged feature specs into project memory with provenance, sweep discovery, and gated cleanup

Scans local repositories and a Supabase database to inventory all pathway, portal, and theme content, producing a categorized report organized by portal.

Creates NFT collections with metadata generation, IPFS storage, and minting contract deployment

Audits image assets across a project to find missing, broken, or mismatched images, and generates prompts for missing assets.

Ownership models are usually inherited rather than chosen, and the inherited one

Use to audit arrears, collections and financial-difficulty conversations for fair treatment — forbearance offered, pressure absent, vulnerability recognised. Trigger for "audit our collections calls", "are we treating customers in arrears fairly", "did we offer forbearance", financial difficulty handling, payment plan conversations, or a complaint about collections conduct.

Periodically scans Claude Code configuration for redundant, stale, or orphaned items and walks the user through a confirm-each-deletion cleanup.

Memory (abaf-memory)

Surveys available blocks from a local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring, returning a block inventory with purposes to inform content modeling decisions.

Action (apaz-action)

Qdrant vector database — collections, upsert, search, filtering, payloads, sparse vectors, BM25

Action (afaz-action)

Mandatory training archive with model gating (APPROVED/REVIEW/DROP). Trigger when: (1) training run completes, (2) need to decide which models to deploy, (3) want historical training reference, (4) need checkpoint recommendations for overfitting.

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.

Visual design and asset creation — social media graphics, HTML/CSS mockups, image generation, text overlays and branding for any active brand