acc-readme-template
Generates README.md files for PHP projects. Creates structured documentation with badges, installation, usage, and examples.
Best use case
acc-readme-template is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generates README.md files for PHP projects. Creates structured documentation with badges, installation, usage, and examples.
Teams using acc-readme-template should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/acc-readme-template/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How acc-readme-template Compares
| Feature / Agent | acc-readme-template | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generates README.md files for PHP projects. Creates structured documentation with badges, installation, usage, and examples.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# README Template Generator
Generate professional README.md files for PHP projects.
## Template Structure
```markdown
# {Project Name}
{badges}
{one-line description}
## Features
{feature list with benefits}
## Requirements
{dependencies and versions}
## Installation
{composer command and setup steps}
## Quick Start
{minimal working example}
## Documentation
{links to detailed docs}
## Contributing
{link to CONTRIBUTING.md}
## Changelog
{link to CHANGELOG.md}
## License
{license type and link}
```
## Badge Templates
### Standard Badge Set
```markdown
[](https://github.com/{owner}/{repo}/actions)
[](https://codecov.io/gh/{owner}/{repo})
[](https://packagist.org/packages/{vendor}/{package})
[](https://packagist.org/packages/{vendor}/{package})
[](LICENSE)
```
### Minimal Badge Set
```markdown
[](https://github.com/{owner}/{repo}/actions)
[](https://packagist.org/packages/{vendor}/{package})
```
## Section Templates
### Features Section
```markdown
## Features
- ✅ **Feature Name** — Brief description of benefit
- ✅ **Feature Name** — Brief description of benefit
- ✅ **Feature Name** — Brief description of benefit
- 🚧 **Coming Soon** — Planned feature
```
### Requirements Section
```markdown
## Requirements
- PHP 8.5+
- Composer 2.0+
- Extensions: ext-json, ext-pdo
### Optional
- Redis (for caching)
- RabbitMQ (for queuing)
```
### Installation Section (Basic)
```markdown
## Installation
```bash
composer require {vendor}/{package}
```
```
### Installation Section (With Config)
```markdown
## Installation
1. Install via Composer:
```bash
composer require {vendor}/{package}
```
2. Publish configuration (optional):
```bash
php artisan vendor:publish --provider="Vendor\Package\ServiceProvider"
```
3. Configure environment:
```bash
# .env
PACKAGE_API_KEY=your-key
PACKAGE_DEBUG=false
```
```
### Quick Start Section
```markdown
## Quick Start
```php
<?php
declare(strict_types=1);
use {Vendor}\{Package}\{MainClass};
// Initialize
${instance} = new {MainClass}();
// Basic operation
$result = ${instance}->doSomething('input');
// Output
echo $result->status; // "success"
```
```
### Documentation Section
```markdown
## Documentation
- 📖 [Getting Started](docs/getting-started.md)
- ⚙️ [Configuration](docs/configuration.md)
- 📚 [API Reference](docs/api/README.md)
- 💡 [Examples](docs/examples/)
- ❓ [FAQ](docs/faq.md)
```
### Contributing Section
```markdown
## Contributing
Contributions are welcome! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for:
- Development setup
- Coding standards
- Testing guidelines
- Pull request process
```
### License Section
```markdown
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
```
## Complete Example
```markdown
# Awesome Package
[](https://github.com/vendor/awesome-package/actions)
[](https://codecov.io/gh/vendor/awesome-package)
[](https://packagist.org/packages/vendor/awesome-package)
[](https://packagist.org/packages/vendor/awesome-package)
[](LICENSE)
A PHP library for processing awesome things with type safety and modern practices.
## Features
- ✅ **Type-Safe API** — Full PHP 8.5 type declarations
- ✅ **PSR Compliant** — PSR-4, PSR-7, PSR-12
- ✅ **Zero Dependencies** — No external runtime dependencies
- ✅ **Fully Tested** — 100% code coverage
## Requirements
- PHP 8.5+
- Composer 2.0+
- ext-json
## Installation
```bash
composer require vendor/awesome-package
```
## Quick Start
```php
<?php
declare(strict_types=1);
use Vendor\AwesomePackage\Processor;
$processor = new Processor();
$result = $processor->process(['data' => 'value']);
echo $result->status; // "success"
```
## Documentation
- 📖 [Getting Started](docs/getting-started.md)
- ⚙️ [Configuration](docs/configuration.md)
- 📚 [API Reference](docs/api/README.md)
- 💡 [Examples](docs/examples/)
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and guidelines.
## Changelog
See [CHANGELOG.md](CHANGELOG.md) for version history.
## License
MIT License - see [LICENSE](LICENSE) for details.
```
## Generation Instructions
When generating a README:
1. **Analyze** the project structure (`composer.json`, `src/`)
2. **Identify** main class/entry point
3. **Extract** dependencies and requirements
4. **Create** minimal working example
5. **Generate** appropriate badges
6. **Link** to existing documentation
7. **Verify** all links point to existing filesRelated Skills
documentation-templates
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
acc-troubleshooting-template
Generates troubleshooting guides and FAQ sections for PHP projects. Creates problem-solution documentation.
acc-getting-started-template
Generates Getting Started guides for PHP projects. Creates step-by-step tutorials for first-time users.
acc-code-examples-template
Generates code examples for PHP documentation. Creates minimal, copy-paste ready examples with expected output.
acc-changelog-template
Generates CHANGELOG.md files following Keep a Changelog format. Creates version history documentation.
absurdist-readme-writer
Toolkit for creating an entertainingly stupid README that manages to give off Tim & Eric, Steve Brule vibes while maintaining a level of technical acumen that is expected of a modern open source project. This skill applies when users request a silly or absurd README.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
employment-contract-templates
Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment docume...
ARM Template Functions
Expert knowledge for using Azure Resource Manager (ARM) template functions, especially reference(), listKeys(), and resourceId() in subscription-level and nested deployments. Use when working with ARM templates, encountering template validation errors, or implementing cross-scope resource references.
templates
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
setup-cdk-templates
Use when creating CLAUDE.md files or .claude/ directories - detects project type, generates appropriate templates, and scaffolds Claude configuration with commands and hooks
readme-updates
Maintain README files with setup instructions, features, tech stack, and usage examples. Use when updating project documentation, adding new features, improving onboarding, or creating READMEs for new packages.