| name | description |
|---|---|
Logging Best Practices |
Use before implementing logs in a medium to large scale production system. |
This skill is adpated from "Logging sucks. And here's how to make it better. by Boris Tane.
When helping with logging, observability, or debugging strategies, follow these principles:
| # Linter will ignore these directories | |
| IGNORE_LINT_DIRS = .venv|venv | |
| LINE_LENGTH = 88 | |
| install_tools: | |
| @echo "$(YELLOW)🔧Installing tools...$(RESET)" | |
| @uv tool install black --force | |
| @uv tool install ruff --force | |
| @uv tool install ty --force | |
| @uv tool install vulture --force |
| description | argument-hint | model | |
|---|---|---|---|
Interview me about the plan |
|
opus |
Read this plan file $1 and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious.
| I'm a [your level] [profession] and I want to learn [topic] so I can [objective]. Follow the RULES below to generate a comprehensive yet concise mini-course for rapid learning. The course should contain chapters that teach me about these SUB_TOPICS. Make sure the chapters fit my level, profession and topic. Ask for clarification if you need more information about my knowledge. | |
| SUB_TOPICS | |
| - [topic 1] | |
| - [topic 2] | |
| - [topic 3] | |
| RULES | |
| - Use concrete examples to explain every concept | |
| - Use emojis to add expression |
Analyze this codebase and create a multi-level interactive dependency graph visualization as a single HTML file.
Level 1 - System Overview (40,000ft view):
Level 2 - Module View (10,000ft view):
Paste it to settings.json:
"github.copilot.chat.commitMessageGeneration.instructions": [
{
"text": "Follow the Conventional Commits format strictly for commit messages. Use the structure below:\n\n```\n<type>[optional scope]: <gitmoji> <description>\n\n[optional body]\n```\n\nGuidelines:\n\n1. **Type and Scope**: Choose an appropriate type (e.g., `feat`, `fix`) and optional scope to describe the affected module or feature.\n\n2. **Gitmoji**: Include a relevant `gitmoji` that best represents the nature of the change.\n\n3. **Description**: Write a concise, informative description in the header; use backticks if referencing code or specific terms.\n\n4. **Body**: For additional details, use a well-structured body section:\n - Use bullet points (`*`) for clarity.\n - Clearly describe the motivation, context, or technical details behind the change, if applicable.\n\nCommit messages should be clear, informative, and professional, aiding readability and project tracking."
}
]
| You are Manus, an AI agent created by the Manus team. | |
| You excel at the following tasks: | |
| 1. Information gathering, fact-checking, and documentation | |
| 2. Data processing, analysis, and visualization | |
| 3. Writing multi-chapter articles and in-depth research reports | |
| 4. Creating websites, applications, and tools | |
| 5. Using programming to solve various problems beyond development | |
| 6. Various tasks that can be accomplished using computers and the internet |
| # train_grpo.py | |
| import re | |
| from datasets import load_dataset, Dataset | |
| from transformers import AutoTokenizer | |
| from peft import LoraConfig | |
| from trl import GRPOConfig, GRPOTrainer | |
| # Load and prep dataset | |
| SYSTEM_PROMPT = """ |
| Classify user search queries as either "Good Google Search Query" or "Bad Google Search Query" based on their likelihood of yielding relevant and helpful results from Google Search. | |
| Input: User search query (text string). | |
| Output: Classification label: | |
| * Good Google Search Query: The query is likely to be effectively answered by Google Search. | |
| * Bad Google Search Query: The query is unlikely to be effectively answered by Google Search. Further categorize "Bad" queries into subtypes for better understanding and classifier training (optional but highly recommended): | |
| * Chit-Chat/Conversational/Social | |
| * Personal/Subjective/Opinion-Based (Un-searchable) | |
| * Vague/Ambiguous/Lacking Specificity |