Use this skill to install, set up, fix, or configure the LCP plugin so its `lcp serve-all` MCP server actually starts and resolves libraries — the configuration side of LCP, not its lookup tools. Reach for it the moment LCP isn't working or needs adjusting, including right after installing the plugin when the user doesn't know what to do next or what belongs in its `.lcp-config.json`. Trigger it when: the lcp MCP server won't start or errors on launch (e.g. `-32000`, "could not resolve a runnable lcp"); LCP can't find, resolve, or load the user's libraries; LCP must launch from a specific lcp binary, venv, pyenv, conda, or Python interpreter; the user wants a private/team registry, a whitelist of served libraries (`expose`), or libraries preloaded at startup for fast first lookups. Treat "get LCP working", "set up LCP", or "fix LCP" as a trigger even when no config file, JSON, or `.lcp-config.json` is named — these are all configuration tasks. Do not use it for running LCP's lookup tools (resolving or browsin
This skill should be used when the user writes code that imports or uses a Python library, asks to "look up the X API", "check how to use X", "what's the signature of X.Y", "resolve library X", or encounters import errors or API misuse. Activates the lcp MCP server's resolve → search → get_symbol workflow for on-demand introspection of any pip-installed package.
This skill should be used when the user writes code against a Python library, asks "how do I use X", encounters an AttributeError or ImportError on a library symbol, or asks "what parameters does X.Y take". Guides the agent to verify APIs through the lcp MCP server's resolve → search → get_symbol workflow before writing code.
Use when writing or updating documentation for the LCP project — new functionality requires docs, existing docs need updating after a feature change, documentation must be created or reorganized in the docs/ folder, or a significant system behavior or data flow changes. Authoritative guideline for LCP documentation conventions (architecture docs, user-facing guides, and the auto-generated API reference).
Use when creating any git commit - enforces structured commit messages with a 3-letter action code, title, and description following the project convention
This skill should be used when the user writes code that imports or uses a Python library, asks to "look up the X API", "check how to use X", "what's the signature of X.Y", "resolve library X", or encounters import errors or API misuse when the lcp universal MCP server is connected. Provides the resolve_library workflow for on-demand introspection of any pip-installed package.
This skill should be used when the user writes code against a Python library, asks "how do I use X", encounters an AttributeError or ImportError on a library symbol, or asks "what parameters does X.Y take". Checks whether the universal lcp server (requires resolve_library first) or a per-library lcp-LIBNAME server is connected and uses it to discover correct APIs, signatures, and parameter types.