sylvadoc Skill
description: Les préférences de Sylvadoc pour la confection de projets web en Nuxt/Vue/Typescript.
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
sylvadoc is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around utility skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is Generic Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in diegosouzapw/awesome-omni-skill, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
---
name: sylvadoc
description: Les préférences de Sylvadoc pour la confection de projets web en Nuxt/Vue/Typescript.
metadata:
author: Sylvadoc
version: "2026.1.29"
---
# Les préférences de Sylvadoc
Ces skills documentent les préférences de Sylvadoc pour la confection de projets web modernes en JavaScript/TypeScript, notamment avec Vue, Nuxt, Vite, et d'autres outils populaires.
## Quick Summary
| Category | Preference |
|----------|--------------------------------|
| Package Manager | pnpm |
| Language | TypeScript (strict mode) |
| Module System | ESM (`"type": "module"`) |
| Linting & Formatting | ESLint & Prettier |
| Testing | Vitest |
| Documentation | VitePress (in `docs/`) |
---
## Stack principal
### Package Manager (pnpm)
Utiliser pnpm comme package manager.
```json
{
"packageManager": "pnpm@latest"
}
```
### TypeScript (Strict Mode)
Toujours utiliser TypeScript avec le mode strict activé.
```json
{
"compilerOptions": {
"target": "ESNext",
"module": "ESNext",
"moduleResolution": "bundler",
"strict": true,
"esModuleInterop": true,
"skipLibCheck": true,
"resolveJsonModule": true,
"isolatedModules": true,
"noEmit": true
}
}
```
### Unit Testing (Vitest)
Utiliser Vitest pour les tests unitaires.
```json
{
"scripts": {
"test": "vitest"
}
}
```
**Conventions:**
- Place test files next to source files: `foo.ts` → `foo.test.ts` (same directory)
- High-level tests go in `tests/` directory in each pack
...