scheduling
io.github.asgeirtj/system_prompts_leaks/scheduling
Find meeting or appointment times, create private calendar holds or invitations, and reschedule or cancel events within the user's authorization. Not for automations.
“Prompt Engineering” 共 409 个结果
io.github.asgeirtj/system_prompts_leaks/scheduling
Find meeting or appointment times, create private calendar holds or invitations, and reschedule or cancel events within the user's authorization. Not for automations.
io.github.asgeirtj/system_prompts_leaks/library
Use ChatGPT Library when the user mentions their Library, asks to find or work with a Library-backed file, Site, or named file that may be in the Library, or wants to organize Library folders, restore a previous version, or share a native Library file or folder. Also use it when the user wants a user-facing file or reusable artifact created or updated, even if they do not mention the Library. It can search and read Library content, bring files into local workflows, save new deliverables, and update existing Library files while preserving their identity and version history.
io.github.asgeirtj/system_prompts_leaks/durable-test-collateral
Load the body before the first implementation edit for a bug fix or behavior change, or when the user or governing specification makes reusable tests a deliverable. It keeps the smallest focused test with the delivered project and updates coverage when behavior changes. Do not load for greenfield work unless reusable tests are explicitly required, behavior-preserving refactors, verification-only work, plan/review/explanation/documentation/formatting/generated-output-only work, explicit no-change or no-tool work, or when the user declines tests.
io.github.asgeirtj/system_prompts_leaks/plan
On an explicit planning request, always call `read_skill` for this skill before answering. Research first, then return one concise inline plan; do not create a plan file unless the user explicitly asks or a governing workflow requires one. Start and end the reply by saying this is not a special mode and `go` executes the plan; do not implement in the planning turn. For ordinary implement, build, fix, debug, or refactor requests, work directly. When an explicit plan divides work into separate diffs, commits, or PRs and the user asks to publish, preserve that split and tell the user before deviating.
io.github.asgeirtj/system_prompts_leaks/requirements-clarification
Clarify a material user-owned product decision before substantive implementation commitments. Use only when request and named/governing evidence still leave a choice that would materially change scope, platform support, user-facing surface, data/API contract, domain values, project placement, or cross-system architecture; also use when a truncated request omits such a choice. On the initial turn, inspect only named or governing requirements evidence, then ask directly without loading: prefer structured input; ask one blocking outcome question or at most three coupled questions; wait. After the answer, load the body before write or delegation. Do not use for implement/build/fix/debug/refactor work when expected behavior is settled, plan/design deliverables owned by Plan, complexity/greenfield/integration alone, agent-owned technical choices, locally discoverable facts, reversible defaults, permission to begin, or stop/no-tool turns. Never re-ask supplied facts or turn clarification into refusal.
io.github.asgeirtj/system_prompts_leaks/taste
Mandatory preflight for web frontend visual design. If available, call read_skill for bundled:taste before the first frontend create or edit tool call whenever creating or visually styling a human-viewed web page, component, app, dashboard, or interactive report. Do not load it for non-visual frontend logic or machine-only HTML. If unavailable, continue without warning. Negative constraints only; user requests and other explicit styles still win.
io.github.asgeirtj/system_prompts_leaks/python-env
Setting up or installing into a Python environment. One rule applies whether or not you read the body - the environment belongs with the project, so create it inside the project directory (.venv) or let uv manage it, and never in a scratch directory like /tmp and never by forcing an install into the system interpreter. Load the body before creating a virtualenv, choosing an installer, or writing run instructions for a Python project.
io.github.asgeirtj/system_prompts_leaks/forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely means cancel the current task.
io.github.asgeirtj/system_prompts_leaks/pdf
Build, revise, or manipulate a fixed-layout PDF (report, guide, one-pager, printable document). Use whenever a build task's artifact kind is pdf, a document build's output format is pdf, or the task reads, merges, splits, crops, or fills an existing PDF, including fillable AcroForms. Covers authoring the print-CSS HTML source, rendering, the geometry and validation gates, existing-PDF manipulation and form filling, and delivery under workspace/your_files.
io.github.asgeirtj/system_prompts_leaks/granola
Search and read Granola meeting notes and transcripts through Granola's OAuth-backed MCP server.
io.github.asgeirtj/system_prompts_leaks/muse_db
Inspect database-backed Muse records for diagnosis and cross-table tracing when purpose-built product tools do not expose the needed state.
io.github.asgeirtj/system_prompts_leaks/lovable
Read, create, edit, and deploy web apps and projects in Lovable. Use to turn a product brief into a working website or prototype, inspect existing project code, update pages and features, and publish changes through Lovable's official MCP server.
io.github.asgeirtj/system_prompts_leaks/vercel
Inspect and manage the user's Vercel websites, web apps, projects, and deployments. Use to read build and runtime logs, investigate production errors and failed deployments, check deployment status, and deploy projects through Vercel's official MCP server.
io.github.asgeirtj/system_prompts_leaks/document
Create, read, edit, or manipulate Word documents (.docx) and Word templates (.dotx). Use whenever a build task's artifact kind is document with the default docx output, or the task mentions a Word doc, .docx, or .dotx, extracts or reorganizes content from one, inserts or replaces images, does find-and-replace in one, or works with tracked changes (redlines) or comments. Covers python-docx generation, raw OOXML editing of existing files, document structure and formatting, and render verification. Not for PDFs, spreadsheets, or Google Docs.
io.github.rohitg00/ai-engineering-from-scratch/release-review
Review Orchard deployment manifests
io.github.rohitg00/ai-engineering-from-scratch/orchard-release
Check deployment evidence and recovery conditions.
io.github.asgeirtj/system_prompts_leaks/schedule
Create or update a scheduled task that runs automatically. Use when the user says things like "every day", "each morning", "remind me in an hour", "run this at noon", or wants to reschedule an existing task.
io.github.asgeirtj/system_prompts_leaks/frontend-design
面向已有品牌体系之外作品的美术方向指导。
io.github.rohitg00/ai-engineering-from-scratch/migration-review-skill
当变更新增或修改 migrations/ 下路径时审查数据库迁移文件。合并前使用,收集正向迁移、回滚、锁与数据安全方面的证据。
io.github.EveryInc/compound-engineering-plugin/ce-doc-review
以特定角色视角审阅需求、计划或规格文档。当用户希望改进已有的规划文档时使用。
io.github.asgeirtj/system_prompts_leaks/code-review
按给定强度审阅当前 diff 的正确性缺陷和复用/简化/效率优化(low/medium:更少、高置信度发现;high→max:覆盖更广、可能含不确定发现;ultra:云端多 agent 深度审查)。传 --comment 以行内 PR 评论发布发现,或传 --fix 在审查后将修改应用到工作树。
io.github.asgeirtj/system_prompts_leaks/design-sync
将 React 设计体系推送到 claude.ai/design。运行一个转换器,打包真实组件代码(来自 Storybook 或独立包)并上传。当用户执行 /design-sync 或说 "sync my design system to Claude Design" 时使用。
io.github.jame581/GodotPrompter/mobile-development
在面向 Android/iOS 时使用——导出与签名、权限、插件、应用内购买、广告、应用生命周期、设备特性以及移动性能。
io.github.cnoe-io/ai-platform-engineering/docker-compose-first-install
校验并修复 OSS 首装 Docker Compose 路径。在编辑 docker-compose.yaml、docker-compose.dev.yaml、.env.example、release 镜像标签、Compose profiles、Keycloak/OpenFGA/RAG 默认值或本地一体化安装的首次启动 UI 行为时使用。