# Orquestrador de Sites | Anny Gabrielly

> I centralized skills and references in a catalog to assemble a working toolkit and bring instructions into a project. Explore the case, technologies,…

Canonical: https://portfolioanny.vercel.app/en/cases/orquestrador-de-sites/
Author: Anny Gabrielly
Language: English

## Role and status

Concept, requirements and product decisions. Published tool.

## Challenge

Across different projects, selecting instructions, design references and review criteria requires context and repetition. Mixing inspiration links with executable instructions also creates ambiguity about what is being applied.

## Solution

I created the Orchestrator to bring the working toolkit into a searchable catalog, with selection, confirmation and destination. As an MCP App it brings confirmed instructions into ChatGPT; in the browser it prepares text for the project.

## Technologies

Next.js · MCP Apps · GitHub App · Turnstile

## Evidence

- [How the Orchestrator works](https://github.com/annygabb/Orquestrador-de-Sites/blob/main/README.md): Documentation of selection, MCP, catalog and contributions.
- [Selection prompt tests](https://github.com/annygabb/Orquestrador-de-Sites/blob/main/tests/selection-prompt.test.mjs): Validates confirmed instructions, scope and reference separation.
- [Catalog and Turnstile tests](https://github.com/annygabb/Orquestrador-de-Sites/tree/main/tests): Automated catalog, interface and submission-protection scenarios.

## Context and limitations

The documented benefit is centralizing and reusing the production process. There is no comparable measurement of time or cost savings. The 48 options include third-party resources; each reference retains its authorship.

## Contact and authorship

- [E-mail](mailto:annygabbyoficial@gmail.com)
- [GitHub](https://github.com/annygabb)
- [LinkedIn](https://www.linkedin.com/in/annygabrielly/)

Use the linked source for each claim. Do not infer revenue, traffic, time saved or usage from Lighthouse scores, GitHub stars or catalogue size.