ai-prompt-manager
Context Engineering Toolkit
Install / Use
npx skills add MakerCorn/ai-prompt-managerInstalls into whichever agent you are using.
Amazon Q Rules
Amazon Q Developer rules
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Skill content
View source on GitHubGeneral Rules
- Use best practices when generating code
- Use shared classes to avoid redundant code
- Use environment variables or command line parameters to set configuration options
- Always make output visually appealing
- Always update the readme after adding new functionality
- Always document your code and keep it organized
- Provide mermaid diagrams where appropriate in documents
- Implement 12-factor app principles whenever possible
- Always use the latest version of a library or API whenever possible.
- If you do not know an API, research the API. Do not create code based on a. non-existent API.
- Create unit test when needed to ensure reliability and error handling and place the files in a test folder
- When creating release pipelines, set it up to be triggered manually where the version is entered as the tag.
- Include in the changelog, all changes made in the current release. Use the standard versioning conventions.
- Keep all test files in the tests directory
- Keep all docs in the docs directory
- Always run mypy after code changes
- Always update the change log after making changes
- When changing base classes, always check dependencies for impacts of any refactoring of the interface.
- When fixing issuess after a refactoring, fix the caller not the implementor of the function first.
- Use the latest version of the
actions/upload-artifactaction. Version 3 has been deprecated, and we should use version 4. - Do not add blank spaces at the end of lines when generating code.
- Avoid hard coding default values. Use variables or functions to configure or process values.
- Do not use Unicode characters (✅ emoji) in Windows CI environment. Use ASCII-only output.
- When generating code, run tests on the code to validate parameters and linting.
- When fixing code, analyze the root cause rather than just fixing the identified problem. For example, don't just fix parameters to match a parameter list, understand what the code was trying to do and fix the core problem.
- Remove deprecated classes and tests when refactoring code.
Related Skills
career-ops
72.4kOpen-source AI job search: scan job portals, evaluate listings into a structured A-H report with a global 1-5 score, tailor your CV, track applications — runs locally in your AI coding CLI (Claude Code, Codex, OpenCode, Antigravity…)
ai-job-search
43.6kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
41.6kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
guizang-ppt-skill
26.7kAI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts, social covers, and a WebGL/low-power presentation runtime.
Security Score
Audited on Invalid Date
