10-of-my-most-popular-text-to-image-series-prompts-78b0897e
generate a bunch of images, then you curate the results to handpick the best ones
Enable "Context, not Control" workflow - clarify requirements through multi-turn dialogue, reduce rework, and execute with appropriate permission levels. Use when users want AI to take more autonomy, need help clarifying vague requirements, or want to establish trust-based collaboration patterns. Supports three permission levels (Master/Collaborative/Assistant) and automatic context management.
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
SkillHub CLI
skillhub install 843645440/context-not-control打开来源仓库,查看说明和兼容环境后,按来源提供的命令或步骤安装。
将来源链接提供给你的 Agent,让它先读取说明、核对依赖,并向你说明将执行的安装步骤。
A skill that transforms how you work with AI - from micromanaging every step to providing context and letting AI make decisions. Inspired by the "Context, not Control" philosophy from the OpenClaw community.
Traditional approach: You tell AI exactly what to do, step by step.
This approach: You tell AI what you want to achieve, AI figures out how.
The key insight: AI works best when you give it rich context about your goals, constraints, and preferences - then trust it to execute within appropriate boundaries.
Run the initialization script to set up your project context and permission level:
python scripts/init_context.py
This creates:
PROJECT.md - Your project context (goals, constraints, preferences)PERMISSION_CONFIG.yaml - Your permission boundariesChoose one of three levels:
Level 1 - Master Mode (Full autonomy)
Level 2 - Collaborative Mode (Balanced, recommended)
Level 3 - Assistant Mode (High control)
Instead of detailed specifications, start with what you want:
"I need a team chat tool"
AI will ask clarifying questions:
这些信息来自收录时的来源分析,可能滞后;使用前请核对最新来源文件。
# Context, not Control A skill that transforms how you work with AI - from micromanaging every step to providing context and letting AI make decisions. Inspired by the "Context, not Control" philosophy from the OpenClaw community. ## Core Philosophy **Traditional approach**: You tell AI exactly what to do, step by step. **This approach**: You tell AI what you want to achieve, AI figures out how. The key insight: AI works best when you give it rich context about your goals, constraints, and preferences - then trust it to execute within appropriate boundaries. ## When to Use This Skill - Starting a new project with vague requirements - Want to reduce back-and-forth and rework - Need AI to take more initiative and make decisions - Want to establish clear permission boundaries - Transitioning from "micromanaging AI" to "trusting AI" ## Quick Start ### 1. Initialize Your Context Run the initialization script to set up your project context and permission level: ```bash python scripts/init_context.py ``` This creates: - `PROJECT.md` - Your project context (goals, constraints, preferences) - `PERMISSION_CONFIG.yaml` - Your permission boundaries ### 2. Set Your Permission Level Choose one of three levels: **Level 1 - Master Mode** (Full autonomy) - AI makes all technical decisions - Only confirms: spending money, public messages, deleting databases - Best for: High trust, high risk tolerance **Level 2 - Collaborative Mode** (Balanced, recommended) - AI executes most tasks autonomously - Confirms: money, public messages, important deletions, system changes - Best for: Most users, balanced control **Level 3 - Assistant Mode** (High control) - AI provides suggestions and code - Confirms: All operations before execution - Best for: New users, low risk tolerance, learning mode ### 3. Start with Requirements Instead of detailed specifications, start with what you want: ``` "I need a team chat tool" ``` AI will ask clarifying questions: - Who is this for? - Wh...
generate a bunch of images, then you curate the results to handpick the best ones
generate a bunch of images, then you curate the results to handpick the best ones
Productivity system based on Maya calendar with 13 natural tones for project management and personal development
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.