cobogo-consumer-synergy

Analyze Cobogó consumer repositories to detect shared design-system needs and coordinate cross-repo issues and PRs.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill cobogo-consumer-synergy-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cobogo-consumer-synergy
Source: https://github.com/franklinbaldo/skills/tree/main/cobogo-consumer-synergy
Command: npx skills add https://github.com/franklinbaldo/skills --skill cobogo-consumer-synergy-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design-system maintainers often change a shared library in isolation, missing reusable needs, duplicated local solutions, and adoption evidence spread across downstream consumer repositories. This Skill structures that cross-repo analysis so decisions about what belongs in Cobogó versus in each consumer are evidence-based. ## Core Features & Use Cases - Consumer portfolio analysis: Read the registered consumer registry in the OKF corpus and verify facts against real consumer repositories before proposing roadmap work. - Synergy and duplication detection: Identify equivalent unmet needs, duplicated semantic tokens, and local solutions worth upstreaming, while preserving negative evidence when convergence is wrong. - Authority decisions and coordinated execution: Decide whether each change belongs in Cobogó, a consumer, or both, then open scoped issues or reviewable PRs and update the registry with factual adoption state. - Use Case: Two consumers independently maintain equivalent semantic token roles; use this Skill to verify the overlap in both repositories, upstream the generalizable role into Cobogó, open one-surface adoption PRs, and record the outcome in the consumer registry. ## Quick Start Use the cobogo-consumer-synergy skill to compare the registered Cobogó consumers, find duplicated needs, and propose the right issues or PRs in each repository.

Frequently Asked Questions about cobogo-consumer-synergy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect duplicated design-system work across multiple repositories?▼

Read the consumer registry to find reported unmet needs and local solutions, then inspect the actual consumer repositories for equivalent semantic tokens, repeated patterns, or parallel implementations. Confirm the shared product or design relation before proposing any shared abstraction.

How do I decide whether a change belongs in a design system or a consumer app?▼

Change the design system when the capability is reusable across consumers, involves shared semantics, or generalizes a proven local solution. Change the consumer when the work is adoption, branding, domain state, or a local improvement that does not generalize.

When should I open issues versus PRs in consumer repositories?▼

Open issues when analysis reveals a problem that still needs design decisions, stating evidence, authority, and acceptance criteria. Open PRs only when the change is concrete, reviewable, reversible, and grounded in accepted knowledge or strong brownfield evidence.

Can two consumers share a pattern without looking visually identical?▼

Yes. The skill tests for parentage without uniformity: consumers can adopt the same semantic relation or capability while keeping distinct density, branding, and presentation. If a shared abstraction forces visual convergence without a task reason, reduce it.

What are the limitations of registry-based consumer analysis?▼

The registry is an index, not a substitute for inspecting real repositories, and registry membership does not imply code dependency. Adoption status must never be inferred from the mere existence of specimens, issues, or PRs.