Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

workspace-file-system-e2e

Estrelas0

Forks0

Atualizado7 de fevereiro de 2026 às 10:02

End-to-end workflow for implementing workspace file system strategies with permission hardening, concurrent access handling, and AI integration. Use this workflow when implementing file system E2E for IDE, Notes, or Knowledge workspaces.

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

shynlee04

shynlee04/idumb-v2

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	Workspace File System E2E
description	End-to-end workflow for implementing workspace file system strategies with permission hardening, concurrent access handling, and AI integration. Use this workflow when implementing file system E2E for IDE, Notes, or Knowledge workspaces.

Workspace File System E2E Workflow

This Workflow provides Claude Code with step-by-step guidance for implementing workspace file system E2E.

When to use this workflow

When implementing file system E2E for a workspace (IDE, Notes, Knowledge)
When auditing FSA (File System Access API) permission models
When creating agent tool permission matrices
When handling concurrent file access and synchronization
When integrating AI synthesis with workspace file systems

Workflow Steps

Step 1: File System Strategy Definition (2-3 hours)

Agent: workspace-architect Input: Workspace type (IDE, Notes, Knowledge) Output: File system strategy document

Acceptance Criteria:

Desktop strategy defined (FSA API with bi-directional sync)
Mobile strategy defined (IndexedDB with sync-to-FSA)
Permission handling specified (FSA requests, graceful degradation)
Concurrent access strategy defined (file locking, conflict resolution)
AI integration approach defined (per-file, batch, RAG)

Step 2: Permission Model Implementation (3-4 hours)

Agent: workspace-architect Input: File system strategy Output: Permission model + agent tool matrix

Acceptance Criteria:

FSA permission audit completed
Agent tool permission matrix created
Permission request UI implemented (user prompts)
Permission persistence handled (session vs permanent)
Permission revocation support (user can revoke)

Step 3: Concurrent Access Handling (3-4 hours)

Agent: workspace-architect Input: Permission model Output: File locking + conflict resolution

Acceptance Criteria:

File locking mechanism implemented
Conflict resolution strategies defined (last-write-wins, merge, user-choice)
Concurrent operation queuing
Optimistic locking with retry
User prompts for conflicting changes

Step 4: Sync Implementation (4-6 hours)

Agent: file-sync-specialist Input: Concurrent access handler Output: Sync service + status indicators

Acceptance Criteria:

Sync service implemented (bi-directional, batch, throttle)
Sync status indicators created (UI components)
Conflict resolution UI (user choice prompts)
Offline-first support (IndexedDB queue)
Sync error recovery (retry logic, rollback)

Step 5: AI Integration (3-5 hours)

Agent: workspace-architect Input: Sync service Output: AI synthesis integration

Acceptance Criteria:

Per-file AI synthesis implemented
Batch AI synthesis implemented
RAG pipeline integration (Knowledge workspace)
AI tool permissions (read, write with user consent)
Progress indicators for AI operations

Step 6: E2E Validation (2-3 hours)

Agent: workspace-architect Input: Complete E2E implementation Output: Validation report

Acceptance Criteria:

E2E tests passing (critical user journeys)
Permission model validated (all scenarios)
Concurrent access tested (no data loss)
Sync reliability validated (offline, online, conflicts)
AI integration tested (per-file, batch)
Zero data loss scenarios

Example Usage

"Implement Notes workspace file system E2E using the workspace-file-system-e2e workflow"

Validation Commands

# TypeScript check
pnpm tsc --noEmit --incremental

# Test suite
pnpm test

# E2E tests for workspace
pnpm test workspace-*

# File system sync validation
pnpm test sync-*

Success Criteria

✅ File system E2E implemented (read, write, sync)
✅ Permission model hardened (FSA, agent tools)
✅ Concurrent access handled (file locking, conflicts)
✅ AI integration working (per-file, batch)
✅ Sync status indicators visible
✅ Zero data loss scenarios
✅ E2E tests passing

Artifacts

For detailed workflow documentation, refer to: Workspace File System E2E Workflow

Mais deste repositório

mesmo repositório

agent-browser

shynlee04/idumb-v2

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

2026-02-070

gap-analysis

shynlee04/idumb-v2

Systematically identify what's missing, unknown, or needs investigation before making changes or decisions. Use proactively when proposing features, implementing changes, or making technical decisions to ensure all critical areas are covered. This skill catches overlooked dependencies, edge cases, and integration points before they become problems. Examples: - "Implement user authentication" → trigger gap analysis (what's the current auth system?) - "Add caching to API" → trigger gap analysis (what caching infrastructure exists?) - "Migrate to TypeScript" → trigger gap analysis (what's the build pipeline?) - "Refactor this module" → trigger gap analysis (what depends on this module?) - "Add new API endpoint" → trigger gap analysis (what endpoints exist, what patterns?)

2026-02-070

intent-clarification

shynlee04/idumb-v2

Detect ambiguous or underspecified research requests and guide through structured clarification questions before executing any research. Use proactively when user requests are vague, lack specificity, missing context, or have unclear goals. This skill prevents wasted research by ensuring intent is crystal clear before any web searches, file reads, or data gathering. Examples: - "Research the codebase" → ❌ Too vague, trigger clarification - "Why is this slow?" → ❌ Missing context (what is "this"?), trigger clarification - "Add a feature" → ❌ Not research, this is implementation - "Investigate authentication flow" → ❌ What specifically about it? Trigger clarification - "Compare React and Vue" → ✅ Specific enough, but still validate dimensions

2026-02-070

multi-aspect-assessment

shynlee04/idumb-v2

Evaluate requests, proposals, or decisions from multiple dimensions (technical, business, UX, security, performance, maintainability, etc.) to ensure holistic understanding before proceeding. Use proactively when making technical decisions, choosing solutions, or proposing changes. This skill prevents single-minded thinking and uncovers trade-offs, risks, and opportunities across all relevant aspects. Examples: - "Use Redis for caching" → assess multiple aspects (performance, cost, complexity, ops) - "Add AI to our app" → assess aspects (technical feasibility, user experience, data privacy) - "Refactor to microservices" → assess aspects (benefits, costs, migration complexity, team readiness) - "Implement authentication" → assess aspects (security, UX, integration effort, maintenance) - "Switch to React 19" → assess aspects (benefits, migration cost, breaking changes, learning curve)

2026-02-070

opencode-primitive-selector

shynlee04/idumb-v2

Choose the right OpenCode primitive (Command, Skill, Tool, Prompt, CustomTool, Plugin hook) for a given task or workflow. Use proactively when deciding which OpenCode capability to use, or when trying to understand what's available. This skill maps research and development needs to appropriate OpenCode mechanisms, ensuring optimal use of the platform's capabilities. Examples: - "How do I search the codebase?" → select tool (read/grep) - "I need a reusable workflow for feature development" → select command - "How do I intercept file writes?" → select plugin hook - "What primitive should I use for systematic debugging?" → select skill - "I need a custom tool for X" → select CustomTool (if innate tools insufficient)

2026-02-070

research-workflow-planner

shynlee04/idumb-v2

Create structured, executable research plans with clear phases, checkpoints, and validation criteria. Use proactively when research intent is clear but execution plan is missing. This skill transforms research goals into actionable workflows with defined deliverables, time estimates, and success metrics, ensuring research is systematic and produces useful outputs. Examples: - "Research how to add OAuth" (intent clear, need plan) → trigger workflow planner - "Investigate performance bottlenecks" (intent clear, need plan) → trigger workflow planner - "Analyze codebase architecture" (intent clear, need plan) → trigger workflow planner - "Find best practices for X" (intent clear, need plan) → trigger workflow planner - "Compare technology options" (intent clear, need plan) → trigger workflow planner

2026-02-070

Execute qualquer Skill com um clique