Sean Madrid

isShape Machine
WorkAboutServicesCollaborate
WorkAboutServicesCollaborate
Challenge
Solution
Key Takeaways

From Plain English to GraphQL

CoQuery: AI-Powered Blockchain Query Composer

An experimental interface designed to lower the barrier between blockchain developers and the data they need. CoQuery combines natural language prompts with a curated insight feed, generating ready-to-run GraphQL queries from plain English descriptions. Built as a pilot to test whether proactive, context-aware tooling could replace the traditional assistant model in technical environments.

Challenge

Blockchain developers face a steep learning curve when querying on-chain data. GraphQL syntax, schema navigation, and API documentation create friction between intent and execution. Most tools assume you already know what you're looking for and how to ask for it. For exploratory work or cross-chain analysis, that assumption breaks down fast.

Opportunity-Risk Trade-Off chart for product features and components. There's a green box around the five highest opportunity, low-lift features. There's a red box around the two lowest opportunity, high-lift features.
Opportunity-Risk Trade-Off chart specific to the source of AI expertise to integrate with the product. There's a green box around the three highest opportunity, low-lift features. There's a red box around the three lowest opportunity, high-lift features.

Opportunity-Risk Trade-Off chart for product features and components

Solution

CoQuery bridges the gap with two complementary mechanisms. First, a natural language interface that accepts plain English prompts and generates executable GraphQL queries. Developers describe what they want; the system translates intent into syntax. Second, a curated insight feed that surfaces emerging trends by combining real-time on-chain activity with off-chain signals like GitHub commits and token metadata. Each insight arrives with a pre-built query, ready to explore or adapt.

UI design for the CoQuery pilot

Key Takeaways

Proactive systems demand better feedback mechanisms than assistants do

Thumbs up and thumbs down don't capture what makes an insight relevant or a query useful. Designing around more nuanced signals became central to understanding product fit.

Context-aware tooling changes the interaction model

When the system anticipates need rather than waiting for a question, the interface stops feeling like a conversation and starts feeling like collaboration. That shift requires rethinking how developers encounter and engage with the tool.

Insight relevance depends on external signal quality

GitHub activity, transaction volume, and metadata all contribute to ranking heuristics, but noisy data degrades trust fast. Validating signal sources became as important as the ranking logic itself.

More Side Projects

Popup Piano Bar Songbook

View project