35 lines
1.8 KiB
Markdown
35 lines
1.8 KiB
Markdown
---
|
|
name: workflow-management
|
|
description: Specialized skill for creating, updating, and validating workflow documents in the Gemini Workflow Framework.
|
|
---
|
|
|
|
# Workflow Management Skill
|
|
|
|
This skill allows Gemini to efficiently manage the lifecycle of project workflows.
|
|
|
|
## Functions
|
|
|
|
1. **Workflow Creation**: Propose new workflows using the standardized format (Objective, Action Items, Verification).
|
|
2. **Step Mapping**: Automatically map high-level project goals to discrete, verifiable workflow steps.
|
|
3. **Public Audit**: For each step, identify and link to the relevant public documentation (e.g., GitHub, MDN, public API docs).
|
|
4. **Consistency Check**: Ensure that all action items align with the "Public Constraint Protocol" in `GEMINI.md`.
|
|
|
|
## Standard Workflow Format
|
|
|
|
### Workflow: [Name]
|
|
|
|
#### Step [X]: [Objective Summary]
|
|
- **Goal**: [Detailed goal]
|
|
- **Action Items**:
|
|
- [ ] [Specific task]
|
|
- **Verification**: [Public-domain method to verify success]
|
|
|
|
---
|
|
|
|
## Pitfalls & Best Practices
|
|
|
|
- **Avoid Absolute Positioning in Layouts**: When customizing themes, prefer Flexbox or Grid over `position: absolute` for structural elements like Sidebars or TOCs to prevent content overlap and preserve responsive layout integrity.
|
|
- **Global Theme Settings**: For TOC rendering in Blowfish, rely on `params.toml` configuration (`showTableOfContents = true`) rather than custom Markdown shortcodes (`[TOC]` or `{{< toc >}}`), which are often theme-incompatible.
|
|
- **Custom CSS vs Theme Overrides**: Always use `assets/css/custom.css` for structural overrides. Never modify theme-internal files (`themes/blowfish/...`), as they will be overwritten during updates.
|
|
- **Container Widths**: When overriding container widths, use relative units (percentages) and `!important` sparingly to avoid breaking theme-defined responsive breakpoints.
|