ase-arch-discover

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md

Discover Components *Discover* additional, *third-party components* (libraries/frameworks) for the technology stack to *provide* the *needed functionality* $ARGUMENTS. 1. - Derive the needed from the , but keep the functionality description very *brief* but still *precise*.

-   If <functionality/> is not clear or not precise enough, raise
    questions to the user with the help of an interactive user dialog tool.

-   Display the determined final functionality with just the following
    <template/>:

    <template>
    &#x1F535; **FUNCTIONALITY**: <functionality/>
    </template>
</step>

2. - Determine the used technology stack:

    -   If a file `package.json` is found in the top-level directory
        of the project and contains an entry `typescript` under `dependencies`
        or `devDependencies`, then <stack>TypeScript</stack>.

    -   Else, if a file `package.json` is found in the top-level directory
        of the project, then <stack>JavaScript</stack>.

    -   Else, if a file `build.gradle.kts` or `settings.gradle.kts`
        is found in the top-level directory, then <stack>Kotlin</stack>.

    -   Else, if a file `build.gradle` is found in the top-level directory and
        is applying `kotlin`, `org.jetbrains.kotlin.jvm`, `kotlin-android`,
        or `kotlin-multiplatform` plugins, then <stack>Kotlin</stack>.

    -   Else, if a file `pom.xml` is found in the top-level directory and
        contains `kotlin-maven-plugin` or `kotlin-stdlib` dependencies, then
        <stack>Kotlin</stack>.

    -   Else, if a file `pom.xml` or `build.gradle` is found in the top-level directory
        of the project, then <stack>Java</stack>.

    -   Else, use <stack>Unknown</stack>.

-   Display the determined final technology stack with just the
    following <template/>:

    <template>
    &#x1F535; **TECHNOLOGY STACK**: <stack/>
    </template>
</step>

3. - From and , derive essential keywords (L=1-M), which allow you to search for suitable components.

-   In the to be discovered result set of components <component-K/>
    (K=1-N), remember the component name as <name-K/>, the
    official package name as <package-K/>, the latest version as
    <version-K/>, the stars as <stars-K/>, the created date as
    <created-K/>, the last updated date as <updated-K/>, the total
    number of downloads in the last month as <downloads-K/>.

-   If <stack/> is "JavaScript" or "TypeScript":

    -   Based on the essential keywords <keyword-L/> (L=1-M),
        use the `ase-meta-search` skill in a subagent to *generally*
        discover an initial set of a maximum of 12 *NPM packages*
        <component-K/> and at least their real name <name-K/> and
        their unique package names <package-K/>.

    -   Use the shell command `npm search --json --searchlimit 12
        "<keyword-1/>" [...] "<keyword-M/>"` to *specifically*
        discover an additional set of a maximum of 12 *NPM packages*
        <component-K/> and at least their unique package names
        <package-K/>, based on the essential keywords <keyword-L/>
        (L=1-M). Merge the results into the already existing result
        set, but deduplicate entries.

-   If <stack/> is "Java" or "Kotlin":

    -   Based on the essential keywords <keyword-L/> (L=1-M),
        use the `ase-meta-search` skill in a subagent to *generally*
        discover an initial set of a maximum of 12 *Maven packages*
        <component-K/> and at least their real name <name-K/> and
        their unique Maven coordinates <package-K/> of the form
        `groupId:artifactId`.

    -   Use the shell command `curl -s 'https://search.maven.org/solrsearch/select?q=<keyword-1/>+<keyword-M/>&rows=12&wt=json'`
        to *specifically* discover an additional set of a maximum
        of 12 *Maven packages* <component-K/> and at least their
        unique Maven coordinates <package-K/> (i.e. `<g/>:<a/>` from
        each result document's `g` and `a` fields), based on the
        essential keywords <keyword-L/> (L=1-M). Merge the results
        into the already existing result set, but deduplicate
        entries by Maven coordinate.

-   Call the `ase_component_info(stack: "<stack/>", components:
    [ "<package-1/>", ..., "<package-N/>" ])` tool of the `ase` MCP
    server *once* for the entire set of discovered packages.
    The tool dispatches internally on <stack/> and fetches all
    metadata in maximum parallel and returns an array of objects `{
    name, version, created, updated, repository, stars, downloads,
    rank }`. For each
    component <component-K/> (K=1-N) read from its corresponding
    entry: <version-K/> from `version`, <updated-K/> from `updated`,
    <created-K/> from `created`, <repository-K/> from `repository`,
    <stars-K/> from `stars` (numeric or `N.A.`), <downloads-K/>
    from `downloads` (numeric or `N.A.`) and <rank-K/> from `rank`
    (numeric).

-   Sort, in descending order, the discovered components
    <component-K/> (K=1-N) by their `rank` field and trim the result
    list to just a maximum of 12 total components.

-   For each component <component-K/> (K=1-N), research and then
    decide which *one* of *USP* (Unique Selling Point -- what makes
    it unique), *Crux* (what you should notice), or *Gotcha* (what
    you should not stumble over) is its single most distinguishing
    perspective, and remember this as an <info-K/> (K=1-N) formatted
    like `<type/>: <hint/>` where <type/> is one of `USP`, `Crux`,
    or `Gotcha` and <hint/> is a 1-6 word hint. Do not output
    anything.
</step>

4. - Display the determined, individual components as a Markdown table with just the following