Skip to content
cccskills
FreePublished on GitHub

cto-consultation

Load when the user asks for CTO advice on feature strategy, architecture direction, build-vs-buy, infrastructure, market positioning, roadmap, self-hosting, cost, or organizational tradeoffs; not for reviewing an existing implementation-plan workstream.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.8 KB
  • resources/consultation-framework.md8.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- ABOUTME: CTO consultation skill for product, architecture, infrastructure, and market-facing feature decisions. --> <!-- ABOUTME: Grounds strategic advice in the ISLAMU Event architecture, governance docs, and self-hosting constraints. -->

Must-Read Docs

Top 5 Invariants

  1. The recommendation must preserve the platform promise: enterprise-grade, self-hostable, tenant-governed, and usable by both small communities and larger operators.
  2. Product advice must separate Instance, Tenant, Organization, Group, User, BFF, Client, and API authority instead of collapsing them into one admin or UI concept.
  3. Infrastructure advice must treat optional dependencies as explicit deployment-mode or tier choices with health, fallback, and operator documentation impacts.
  4. UX advice must keep HAL links as the source of truth for per-resource action affordances and keep the API as the hard authorization boundary.
  5. Extensibility advice must choose Layer 1 core fields, Layer 2 typed sector schema, or Layer 3 governed custom properties before proposing storage or UI shape.

Top 5 Anti-Patterns

  1. Enterprise-only default, which raises the operational floor and harms single-organization or community self-hosters.
  2. Local-role UX gating, which duplicates server authorization and breaks the HAL affordance contract.
  3. Runtime-schema sprawl, which turns Layer 3 custom properties into a hidden domain model and bypasses typed policy semantics.
  4. Dashboard-as-source-of-truth, which mistakes infrastructure internals such as scheduler dashboards for product/operator state.
  5. Undated market claims, which make competitive or legal recommendations stale and unverifiable.

Minimal Examples

Consultation output shape:
1. Decision needed
2. Current repo facts
3. Options
4. Recommendation
5. Enterprise/self-hosting impact
6. Implementation path
7. Verification and documentation impact
Example stance:
Quartz.NET is the single internal scheduler, including for Basic Dispatch Mode. Its status surface stays optional, instance-admin-only, and never the source of truth for email delivery state — `EmailDispatchOutbox` is.

Verification Hooks

  • dotnet build --configuration Release --verbosity quiet

Related Skills

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Load for Blazor/MudBlazor UI changes involving forms, dialogs, focus, keyboard navigation, landmarks, ARIA, color contrast, RTL-safe styling, or WCAG 2.2 AA tests; not for backend-only changes.

The English summary is being prepared. Showing the original description.

islamu-ngo/Event8Updated Oct 21, 2026

Load when a task asks to research, verify, compare, or look up framework/package behavior, release notes, standards, RFCs, CVEs, or unfamiliar APIs; use repository evidence first, then official docs, and not for codebase navigation alone.

The English summary is being prepared. Showing the original description.

islamu-ngo/Event8Updated Oct 21, 2026

aspire

Free

Load for Aspire AppHost work: start/stop/wait resources, inspect dashboard/logs/traces, add integrations/resources, rebuild a service, run isolated worktrees, or diagnose Aspire orchestration; not for plain dotnet apps, container-only deployments, or cloud deployment.

The English summary is being prepared. Showing the original description.

islamu-ngo/Event8Updated Oct 21, 2026

Load for authentication or authorization changes involving BFF cookies/tokens, JWT validation, claims/user ID extraction, policies, handler access checks, impersonation, or 401/403 bugs; not for UI affordance gating alone.

The English summary is being prepared. Showing the original description.

islamu-ngo/Event8Updated Oct 21, 2026

Load for Blazor BFF server work involving YARP proxy routes, cookie sessions, access-token forwarding/refresh, downstream API calls, BFF handlers, or browser-to-API auth failures; not for client component rendering or API JWT validation alone.

The English summary is being prepared. Showing the original description.

islamu-ngo/Event8Updated Oct 21, 2026

Load when editing Blazor `.razor.css`, scoped selectors, `::deep`, BEM class names, RTL/logical CSS properties, or styling nested MudBlazor components; not for global design tokens or non-Blazor CSS.

The English summary is being prepared. Showing the original description.

islamu-ngo/Event8Updated Oct 21, 2026

See all skills by islamu-ngo

Report a problem with this skill