@alextech Please see https://github.com/zfcampus/zf-apigility-skeleton#qa-tools
I think it is like that on purpose.

I never noticed that section. Seemed like a bug having fundamental workflow not work out of the box. At least MVC skeleton prompts you about it. And why does expressive have it out of the box too https://github.com/zendframework/zend-expressive-skeleton/blob/master/composer.json#L30 ? Shouldn't we be consistent across components?

I think consistency is important, especially when docs says one component is based on the other and developers interchange between tools. This is the user facing docs that makes the statement: https://apigility.org/documentation . No one will look into sources beyond that, especially if you use curl installer on the installation docs, that does not even give a hint its using zf-apigility-skeleton to look for further info. I ended up here purely on a hunch. I know my way around Zend MVC, I am told Apigility uses ZF, I try it for the first time expecting same experience, and cannot get anything to work.

Then there is IDE complaining about missing namespaces on a clean project that looks bad. Took me over hour to figure out why there are missing classes warnings in the skeleton.

Merged to develop for release with 1.5.0.