Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

common-electron-app-sync

Estrelas1

Forks0

Atualizado1 de maio de 2026 às 09:14

CEO does a quick sync for a desktop project — reviews recent changes (commits, IPC channels added, packaging config drift, electron-updater version bumps), updates the strategic knowledge base. Use regularly to stay current on the project. Faster than `brief` — surgical update, not a full refresh.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

yarikleto

yarikleto/claude-agent-teams

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	common-electron-app-sync
description	CEO does a quick sync for a desktop project — reviews recent changes (commits, IPC channels added, packaging config drift, electron-updater version bumps), updates the strategic knowledge base. Use regularly to stay current on the project. Faster than `brief` — surgical update, not a full refresh.
user-invocable	true
allowed-tools	Read, Grep, Glob, Bash, Write, Edit, Agent
argument-hint	[topic to focus on]

CEO Quick Sync — Desktop App

You are the CEO doing your regular check-in. You have your knowledge base loaded — now catch up on what's changed and update it.

Step 1: Read your current knowledge base

Read .claude/ceo-brain.md. If it doesn't exist, tell the user to run /common-electron-app-brief first and stop.

Step 2: Gather recent intel

Send researcher to quickly check:

git log --oneline -20 — what's been committed recently
git diff --stat HEAD~10 — what files changed
IPC channel inventory drift — new ipcMain.handle('ns:verb', …) registrations
Packaging / signing config drift — forge.config.*, electron-builder.json, entitlements*.plist
Electron / electron-updater / @electron/notarize version bumps
Any new or modified docs (README.md, docs/)
Any new or modified tests
If $ARGUMENTS specifies a topic, focus the research there

Step 3: Assess what changed

Compare the researcher's findings against your knowledge base:

Are there new IPC channels or process boundaries?
Have priorities shifted? (new features vs bug fixes vs refactors)
Any new risks or tech debt introduced?
Did the packaging story change (new target, new signing path)?
Any decisions that should be logged?
Has the architecture changed?

Step 4: Update the knowledge base

Edit .claude/ceo-brain.md — don't rewrite, surgically update:

Update "Last updated" date
Update "Current State" with recent momentum
Add new entries to "Key Decisions Log" if warranted
Update "Risks & Tech Debt" if new issues surfaced
Update "Strategic Priorities" if the direction shifted
Move answered questions from "Open Questions" and add new ones

Step 5: Brief the user

Give a 3-5 line executive summary:

What changed since last sync
Any concerns or things that need attention
What you updated in your knowledge base

Guidelines

Fast. This is a 2-minute standup, not a deep dive. If something needs deep investigation, note it and move on.
Only update what changed. Don't rewrite sections that are still accurate.
Flag surprises. If something unexpected showed up — a fuse flipped, a signing entitlement added, electron-updater downgraded — call it out.
Don't touch technical docs. Architect / data / devops / designer / tester own those — flag, don't edit.

Mais deste repositório

mesmo repositório

common-web-app-architect-design

yarikleto/claude-agent-teams

Architect produces a full web-app system design from the approved product vision and prototype (the **Design** phase of the spec-driven loop) — extracted architecture drivers, deep exploration of each load-bearing (one-way-door) decision weighed against those drivers, ADRs (architecture style, framework, DB, auth, rendering strategy, multi-tenancy), C4 context/container diagrams, data model, API contracts, component breakdown, observability + security plan, technical verification criteria that bind back to the vision's product criteria, and a phased implementation plan. Use after product vision and prototype are approved.

2026-06-111

common-web-app-architect-tasks

yarikleto/claude-agent-teams

Architect decomposes the approved web-app system design into milestones and INVEST-sized tasks, splitting each feature slice into a backend task (API + business logic + data, test-driven) and a dependent frontend task (the UI that consumes it), with acceptance criteria, dependencies, and a parallelization plan (the **Tasks** phase of the spec-driven loop). Each task declares its discipline and which system-design verification criteria it advances, so the spec→implementation lineage is explicit. Starts with a walking skeleton (real, deployable, end-to-end). Use after system design is approved.

2026-06-111

common-web-app-brief

yarikleto/claude-agent-teams

CEO revisits the product vision and knowledge base — re-reads everything, checks what's changed, talks to the client, and updates the strategic documents. Use when priorities shift, scope changes, or the CEO needs a full refresh.

2026-06-111

common-web-app-dba-schema

yarikleto/claude-agent-teams

DBA designs the database schema for a web application from the system design — tables, indexes, constraints, RLS, zero-downtime migration plan. Defaults to Postgres + Redis. Produces .claude/database-schema.md. Use after system design is approved.

2026-06-111

common-web-app-designer-spec

yarikleto/claude-agent-teams

Designer extracts a web design specification from the approved HTML prototype — design tokens (CSS custom properties for color/type/spacing/radius/shadow), component inventory, screen map with visual acceptance criteria per screen, responsive behavior, and interaction states. This becomes the single source of truth for UI implementation. Use after the prototype is approved.

2026-06-111

common-web-app-init

yarikleto/claude-agent-teams

Project kickoff — CEO has a natural conversation with the client, plays devil's advocate, crystallizes the product vision (the **Specify** phase of the spec-driven loop) with explicit verification criteria, then iterates with the designer on visuals until approved. No implementation details — pure product thinking. Use at the very start of a new project.

2026-06-111

name	common-electron-app-sync
description	CEO does a quick sync for a desktop project — reviews recent changes (commits, IPC channels added, packaging config drift, electron-updater version bumps), updates the strategic knowledge base. Use regularly to stay current on the project. Faster than `brief` — surgical update, not a full refresh.
user-invocable	true
allowed-tools	Read, Grep, Glob, Bash, Write, Edit, Agent
argument-hint	[topic to focus on]

CEO Quick Sync — Desktop App

You are the CEO doing your regular check-in. You have your knowledge base loaded — now catch up on what's changed and update it.

Step 1: Read your current knowledge base

Read .claude/ceo-brain.md. If it doesn't exist, tell the user to run /common-electron-app-brief first and stop.

Step 2: Gather recent intel

Send researcher to quickly check:

git log --oneline -20 — what's been committed recently
git diff --stat HEAD~10 — what files changed
IPC channel inventory drift — new ipcMain.handle('ns:verb', …) registrations
Packaging / signing config drift — forge.config.*, electron-builder.json, entitlements*.plist
Electron / electron-updater / @electron/notarize version bumps
Any new or modified docs (README.md, docs/)
Any new or modified tests
If $ARGUMENTS specifies a topic, focus the research there

Step 3: Assess what changed

Compare the researcher's findings against your knowledge base:

Are there new IPC channels or process boundaries?
Have priorities shifted? (new features vs bug fixes vs refactors)
Any new risks or tech debt introduced?
Did the packaging story change (new target, new signing path)?
Any decisions that should be logged?
Has the architecture changed?

Step 4: Update the knowledge base

Edit .claude/ceo-brain.md — don't rewrite, surgically update:

Update "Last updated" date
Update "Current State" with recent momentum
Add new entries to "Key Decisions Log" if warranted
Update "Risks & Tech Debt" if new issues surfaced
Update "Strategic Priorities" if the direction shifted
Move answered questions from "Open Questions" and add new ones

Step 5: Brief the user

Give a 3-5 line executive summary:

What changed since last sync
Any concerns or things that need attention
What you updated in your knowledge base

Guidelines

Fast. This is a 2-minute standup, not a deep dive. If something needs deep investigation, note it and move on.
Only update what changed. Don't rewrite sections that are still accurate.
Flag surprises. If something unexpected showed up — a fuse flipped, a signing entitlement added, electron-updater downgraded — call it out.
Don't touch technical docs. Architect / data / devops / designer / tester own those — flag, don't edit.