- What is 1994/ghostwriter-core and what does it do?
- 1994/ghostwriter-core is the shared core of the Ghostwriter suite for AI-assisted writing and content workflows. It provides draft text handling, prompt management, an AI provider abstraction, Studio model jobs, schema and layout algorithms, store contracts, photo search, and image placeholders. In a Laravel product it works best as an inner domain library behind your own module rather than as a turnkey package with service providers, Eloquent models, migrations, and HTTP endpoints.
- How do I install ghostwriter-core in a Laravel app?
- Install it with composer require 1994/ghostwriter-core after checking the PHP and dependency constraints in its composer.json. Because package metadata and documentation are sparse, pin a specific commit or version before adding it to a production application. After installation, expect to write your own adapters for stores, AI providers, and photo search rather than publishing config or running migrations.
- Is ghostwriter-core a Laravel package or a framework-agnostic library?
- The core is framework-free: it contains domain and application logic for text handling, prompts, AI providers, schema and layout algorithms, and store contracts without depending on Laravel. That reduces framework lock-in but increases integration work because persistence, queues, configuration, auth, tenancy, and observability remain your responsibility. Treat it as a Composer library inside a Laravel module, not as the application foundation.
- Which PHP and Laravel versions does ghostwriter-core support?
- The supported PHP and Laravel versions are not clearly documented in the overview, so verify the constraints in composer.json before committing. Because the core is framework-agnostic, direct Laravel version conflicts are less likely, but your adapters must still match the package's contracts for stores, jobs, prompts, and schema objects. Confirm PSR interface compatibility and the full dependency tree as part of your evaluation.
- How do I bind Ghostwriter store contracts to Eloquent models?
- Implement adapter classes that satisfy the Ghostwriter store contracts and delegate to Eloquent models or the database query builder. Keep a thin anti-corruption layer at the boundary so upstream domain types do not leak into your application models or controllers. Start by binding a single store adapter in a spike, then map the remaining contracts once the shape of the data is clear.
- Which AI providers does the Ghostwriter provider layer support?
- The package exposes an AI provider abstraction rather than a single hard-coded vendor, so you can wrap provider calls with Laravel's HTTP client and queue infrastructure. The exact list of supported providers is not documented in the overview, so inspect the provider layer and reference addons before assuming coverage. Failover and retries are your responsibility but can be added cleanly by implementing the provider interface with your own fallback logic.
- Does ghostwriter-core include migrations, routes, or queue jobs?
- No: the core deliberately ships no migrations, routes, controllers, queue jobs, or publishable config. Studio model jobs, schema validation, persistence, and provider configuration all need to be bound and executed through your Laravel application. Plan for adapter work and Laravel-native queues, storage, validation, and config instead of expecting a drop-in package.
- Can I use ghostwriter-core with Filament, Statamic, or Craft?
- Separate Ghostwriter addons exist for Statamic, Filament, and Craft, and they are useful as reference implementations of the core contracts. They are distinct packages and should not be assumed production-ready or mature without review. If your admin stack is Filament, evaluate the Filament addon first and use the core directly only when you need a custom integration.
- What license is ghostwriter-core under, and can I use it commercially?
- The repository currently reports NOASSERTION for its license, which is not an approved state and requires legal review before the dependency is merged. Commercial use, redistribution, and fork rights are therefore unclear until the maintainer clarifies the terms. Do not ship it to production until your legal or open-source review process confirms the license.
- How do I test or spike a ghostwriter-core integration safely?
- Run a time-boxed spike outside production: install the package, bind one store adapter, generate a draft from a prompt through one AI provider, persist it, render a schema or layout, and exercise the image-placeholder fallback. Compare the result against building the same narrow workflow internally, and keep your own interfaces at the boundary if you proceed. Also note maturity signals such as zero stars, zero dependents, and a future-dated release, and plan a vendor-or-fork policy with a documented patch process in case upstream stalls.